Not really - it’s exactly just what I’d expect to see from a system that’s not able to keep up with what it’s been asked to do. It’s slowly getting further and further behind until it’s too far and Sonic Pi gives up and kills the thread.
OK, so I tested this on 3 of my machines now and found 1 that exhibits this behaviour, so that’s something. It worked just fine on my powerful PC tower, on my tablet but not on my old ASUS UX301LAA which has an i7-4500U CPU.
I also managed to reduce the code that triggers this down to:
loop do
4.times do
synth :dsaw, release: 0.1, note: :e3
end
sleep 0.125
end
It’s been a while and I’ve been super busy with work (grading 150 student assignments in two weeks does that to you), and when I tried just now, the issue is gone. I tried downloading the 3.1 and 3.2.2 portables, and they showed no issues. Intrigued, I tried my install again, and the issue is gone. I have no idea how. The vc_redist.x64.exe library(?) is installed on my system, probably by a game. I have also installed the automatic updates since then: this one and this one. I will try removing the redist and see if that replicates the issue.
EDIT: Nope, uninstalling the redistributable didn’t break Sonic Pi (running the code at 1000 bpm. It breaks at 1500 bpm). Guess it must have been something in an update or something. Very mysterious.
EDIT 2: Nope, still messes up. But not all the time
I’m guessing you mean v3.1? Because I’m not even sure how to get v2.1 now.
I just downloaded and installed v3.1 portable, and I get the same behaviour - it dies after just over 7 seconds using your reduced code.
Okay, new development. I sat down to practise a bit just now, and the issue is back. It seems like it’s one of those bugs you can’t track down completely.I still haven’t done my complete re-install so it’s a windows home edition to begin with. I’ll see to it this weekend (pinky promise)
The fact that it works/doesn’t work differently on different setups and that there’s no consistency across different versions of Sonic Pi back to 3.1 makes this pretty much impossible to understand.
The only constant appears to be that this only exhibits itself on Windows.
If anyone has any expertise at looking under the hood of Windows applications I’d love any help shedding any light on this matter…