I tried messing around with different installation versions, here’s what I found:
(12; ran fine before upgrading)
13.x: upgraded from 12, ran fine until I recently tried to update-- I specifically remember switching over from a custom dark theme, so I’m certain than some 13.x version ran without issue (still uncertain what exact version it was, hence 13.x; I believe things broke after updating the last week of February?)
(attempted update to 13.? from DirectoryOpus prompt – 13.x was still running here)
13.?: hangs (no windows, no DebugView output WITH registry var set)
(renamed and saved AppData folders, figured it was a config problem)
13.?: crash within 5-10s
(started troubleshooting here)
13.3: crash within 5-10s
13.1: hangs, busyloop on 1 core
13.2: hangs, busyloop on 1
13.3: crashes within 5-10s, as before
(restored original AppData folders)
12: runs fine (and I see DebugView output)
(tried 13.1 in hopes it would run like the very first time I updated to 13.x)
13.1: hangs; cleared AppData again, still fails
13.3: crashes
(reverted to 12.x once more)
To summarize:
12 worked fine (there IS DebugView output)
13.x worked fine until updating
after updating, all 13.[1,2,3] either hang or crash, even if I try restoring the original* AppData folders.
reverting to 12 works fine, but updating to 13.[1,2,3] again causes hang/crash. NO DebugView output
*Note: I only saved the AppData folders after 13.? started hanging, so if it is a config problem, I wouldn’t have expected a config revert to fix it (ie, I do NOT have the config that worked for 13.x, only the hanging 13.?)
I’m running Windows 10, if that makes any difference. Haven’t updated the OS in ages, so no changes there. I’ve downgraded to 12 so I can get back to work at the moment; hopefully we can get DirectoryOpus 13 running without my having to update to Windows 11.
If it’ll help, I might be able to get you the address of the loop that’s hanging in 13.1 and 13.2; without debug symbols it’ll be in the form of
dopus!FUNC+0xADDR
but I’m guessing you guys can convert that on your end.