AngelLoader v1.11.0 - now works better on Wine! (updated 2025/07/24) - by FenPhoenix
fxdwg on 26/12/2024 at 22:38
I'm sorry but this version behaves the same way.
The "AngelLoader_log.txt" output also remains the same with a single line "2024/12/26 14:28:51 1.9.8 (Framework x64) Started session".
I'm assuming that having the "TDMExe" parameter set is what causes your FM scanner to start it's thing with discovering Dark Mod FM's. So I've redone a clean install of TDM (v2.0.12) and have no FM's included, other than what the TDM installer puts there. Even deleting the 3 default FMs doesn't help.
UPDATE:
I just copied the AL v1.98, AL v1.98fixtest1, and TDM to another computer. Both versions don't close right away, but both still close down after about 30 seconds of inactivity (i.e., no messages about fm scanning). The output log remains the same.
UPDATE #2:
I checked the Windows Event Viewer and discovered an entry that might help.
"Application: AngelLoader.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at AL_Common.FileStream_NET.Dispose(Boolean) at AL_Common.FileStream_NET.Finalize()"
FenPhoenix on 26/12/2024 at 23:10
Quote Posted by fxdwg
UPDATE:
I just copied the AL v1.98, AL v1.98fixtest1, and TDM to another computer. Both versions don't close right away, but both still close down after about 30 seconds of inactivity (i.e., no messages about fm scanning). The output log remains the same.
That's extremely bizarre. There's no timer that would trigger something at 30 seconds or any other particular interval, and certainly no timing-related code has been changed since 1.9.7. The only thing that would make AngelLoader do something of its own accord (without user input) is the contents of the TDM FMs folder changing or certain TDM data files changing. But shutting down without either a log message or an error dialog is very unusual behavior and should normally only happen in cases of memory corruption or the code writing off the end off a buffer in unsafe mode or something, where the .NET runtime will shut the app down immediately.
Do you mind troubleshooting with me? I'll make a few different versions with extra logging and we can see at what commit the issue cropped up.
By the way, what version of Windows are you on?
fxdwg on 26/12/2024 at 23:22
I do not mind troubleshooting at all.
I'm on Windows 11 and my other computer I tried afterwards is Windows 10.
FenPhoenix on 26/12/2024 at 23:23
Actually I just was able to reproduce it with a fresh TDM install. I'm looking into it now, I'll give an update in a few...
fxdwg on 27/12/2024 at 00:51
SUCCESS!!
I believe you got it.
fxdwg on 27/12/2024 at 01:26
Well done. V1.9.9 is a winner.
Thanks for jumping on that.
FenPhoenix on 27/12/2024 at 02:00
No problem. If I can't prevent horrific bugs, least I can do is fix 'em quickly. :thumb:
