App crashes on launching it the first time. I’m a new user and freshly downloaded rc30
Expected behavior
App starts after opening it
Steps required to reproduce
After unzipping the RC I started the app and got the error message “Aspect was unexpectedly terminated.” There are no error logs in /temp however I have the system crash report.
I’ve upgraded an Intel Mac mini to the latest OS release and can now see the same behavior – namely it crashing as soon as the first dialog is about to be shown (probably the crash reporter dialog in your case). Interestingly, one of the older releases doesn’t have this issue, so it seems to have been introduced recently as a combination of changes on our side and something in the latest macOS. I’ll see if I can track this down to a certain change on our side, as the actual crash happens somewhere within the system.
We are currently in a bit of a vacation mode and I didn’t manage to track this down my a first attempt last week. But assuming all is going as planned, I expect the next release to be on Monday, and getting this fixed has the highest priority. In case this turns out to be really difficult to track down, the release might get delayed to the following Friday, but we’ll see.
Okay, I see that this is actually a different error code now. I’ve now upgraded the Intel Mac that I used for testing to 5.6.1 and it still works correctly for me, though. Can you have a look whether there is a detailed crash report available? Specifically, the text that follows a line reading “Thread X crashed:: …” would be important, as that should hopefully make it possible to localize where the error happens.
Aspect’s log file (assuming it got far enough to write one) might also be helpful in tracking it down. You can find it by starting the “Terminal” application and entering open $TMPDIR as a command. Then a Finder window should open with a folder that contains the “aspect-log.sdl” log file.
Thanks for sending me the log and crash report! After some research, I could find some similar reports for other applications that appeared to be somehow related to external monitors and invalid window positions. While this didn’t lead to a definitive answer, I’ve prepared a test build that might fix this, and, if not, provides some additional information in the log file that should help to narrow this down:
Okay, it failed in a different place now, but it finally dawned on me where the issue actually is. There is a setting to disable custom window frames, because early Intel GPU drivers had a lot of issues with these. At some point, this setting got broken by seemingly unrelated code change. Now, if you haven’t manually enabled this setting, I’m unsure why it got activated in the first place, because only Windows has code that does that automatically for old Intel drivers, but still, this new build should hopefully fix it:
