But simply put… this most likely leads to a crash. Though, before the crash, there are some weird things that happened and I’d like to point out. I know some others have made a similar report already, but what makes THIS ONE different is, when I reopened studio, the workspace was frozen and I couldn’t select anything (basically, studio takes a snapshot of the current view before minimizing). Re-positioning or resizing the interface does nothing but distort the image.
But studio doesn’t crash right then and there; you can still select things in the workspace and in the other windows, but good luck trying to see them since the main workspace window is completely frozen in the last position it was in.
How to crash: clicking solo, test, stop, create a local server, test server, or any of the above will give the error. There may be other functions that do this but I’ve only done this one for it to crash.
Pressing OK then crashes studio, the background turns white, and the infamous error message pops up…
I’ve been able to reproduce the same bug three times today, each time in the same exact order. If this doesn’t send up a red flag… I don’t know what will.
Good question, to elaborate, I had three instances of studio running in the background, and each one was probably last use maybe 10 or more hours before the glitch occured. Though, afterwards, it’s all straight forward: you’ll know the glitch happens when some things work and others don’t, such as the test in studio button or the workspace window itself. Pressing play solo, or any other method of testing crashes the program and the workspace stays frozen during this.
What I don’t get is why it happens Now. My old computer (Gateway, Windows 8.1) never had this same problem. This one, which is a Dell Inspiron 15 7000, Windows 10, has being doing this a few times since then.
The computer’s a Dell Inspiron 15 7000 Gaming laptop, and yeah, the drivers are as good as new; I haven’t had this computer for a long time either, I’ve only received it two and a half months ago, and it was never marked as used. It doesn’t just happen with an empty baseplate - its mostly happened with complete places - although it can, and it I recently had it happen just three days ago to [nothing but] a baseplate I left idle for a day.
