I can add that when I first ran 17.2.2, it crashed within a few seconds of opening every time. I had to delete my Fusion.prefs file. Maybe if I'd tried resetting the UI first, that would have solved it, but I didn't try it.
Then the other day I suddenly got into the same crash situation, or similar anyway. I opened Fusion and it would suddenly crash within 30 - 90 seconds.
Moving my Fusion.prefs solved it again, so I compared what was different in my current prefs to a backup from a few days earlier. I eventually found the culprit:
- Code: Select all
EnvironmentVars = {
FUSION_Log = "false"
},
Earlier that day I had noticed Help -> Logging, and had enabled it:
It didn't actually seem to generate any extra logs at all. What it did do was cause Fusion Studio to die every time I subsequently opened it.
TLDR: Don't use Help -> Logging! At least on macOS, it adds a Fusion.prefs value that breaks Fusion Studio, and even toggling it off again doesn't fix it, because the mere presence of the EnvironmentVars -> FUSION_Log code I showed above is enough to bring down Fusion.
Attached is a crash log, in case anyone from BMD sees this (when I have time I'll report it direct to BMD support).
I note that the top of the stack trace is:
- Code: Select all
Thread 0 Crashed:: GUI Thread Dispatch queue: com.apple.main-thread
0 libsystem_c.dylib 0x00007fff2034205d __findenv_locked + 52
1 libsystem_c.dylib 0x00007fff20342161 getenv + 54
"findenv" and "getenv" being related to environment variables, which fits with those new lines added to Fusion.prefs - adding (or checking for) FUSION_Log environment variable.
So it would seem that maybe Fusion Studio's environment variable handling is broken in Fusion Studio 17.2.2 - at least on macOS. I've not yet tested Windows.