Isadora 2.5.2 on Win10 weird crash
I want to report a very weird behavior I've experienced with Isadora on Windows 10 Pro.
I've used and tested for months several NUC with Isadora 2.5.2 without any issues. I've packed and parked those computers waiting for the project setup. After a couple of months I've rebooted the computers discovering that Isadora was not able to run anymore, no matter the patch, no Windows update in the meantime, Isadora crashed instantly (I'm attaching the crash report for reference).
The only solution I've found has been installing the 2.6.1 in order to make it run again (converting the patches and discovering other issues with the new version, but this is for another post maybe).
My question is: anyone is able to provide me a logical explanation about this behavior?
Right now I'm not even sure if Isadora 2.6.1 will run again after a bunch of months, not a good feeling.
There is nothing within Isadora that should cause this behaviour outside of an expired license I would think.
Perhaps something has changed on the system during the reboot. I really can't think of another reason. Perhaps checking the release notes for 2.6.1 will show a bug fix that give insight.
@mark mark can you take a look at the attached crash report?
I'd also be interested to know if *anything* is different about your setup this time around.
Did you install new software on the computers? (I know for example Camtwist and the Adobe Cloud can cause issues.)
Are you using any different hardware this time around? (I once thought I had a *huge* problem with Isadora crashing immediately on startup once, but the answer turned out to be my computer and Isadora just didn't like it if the only monitor was a USB monitor.)
I've literally put the computers in a closet a couple of months ago with everything working, now since the first reboot Isadora crashed immediately on 3 different computers.
Tomorrow we'll conduct a test session trying several monitors to see whether it's something related to them.
I'll keep you informed.
Would you mind sending the specs of the NUCs?
Also please feel free to open a support ticket using the link in my signature.
We identified the main issue that caused the Isadora crash in our situation.
Without a proper physical Audio interface connected (speakers or headphone) Isadora wasn't able to run, I suspect it is a Windows issue first but Isadora doesn't try/catch it, though.
Having said that, Isadora is still unstable, both the 2.5.2 and the 2.6.1, sometimes stops to work with a Windows alert, no crash report this time. This is even worse because sometimes the patch runs for hours without issues, sometimes quit unexpectedly after few minutes.
We are using Intel NUC i5-7260U 2.2GHz with 16Gb RAM, Win10Pro.