In the call stack below, if I'm reading it right, it looks like an unhandled exception is being raised in the MsgHandlerWindow's window procedure.
I think it occurs in low-memory conditions. Whether this is a structured exception from OS code or a Delphi exception from madExcept's code (or our code) I can't tell.
We only get these reports when our app is run as .\LocalSystem. (That's not supposed to happen and will stop soon.)
I only mention it in case you think it's worthwhile from madExcept's point of view to catch exceptions here. I'm not too bothered about debugging exactly how our application fails to start when there is no memory
Code: Select all
775d4e93 +0000 ???
776d6cd6 +0081 ntdll.dll RtlRaiseStatus
776afd64 +00f4 ntdll.dll RtlUnwind
0040af36 +00d2 ourapp.exe System 38 +0 @HandleAnyException
776d6cd6 +0081 ntdll.dll RtlRaiseStatus
776d6b62 +000a ntdll.dll KiUserExceptionDispatcher
776d6b3b +002b ntdll.dll KiUserCallbackDispatcher
001ebf36 +002e USER32.dll CreateWindowExA
0041c637 +003f ourapp.exe Winapi.Windows CreateWindowExA
00443b9e +01be ourapp.exe madTools MsgHandlerWindow
00443d59 +0015 ourapp.exe madTools AddMsgHandler_
00443ee8 +0004 ourapp.exe madTools AddMsgHandler
00486931 +0009 ourapp.exe madExcept InitFireHandlers
004b60aa +115e ourapp.exe madExcept Init
01185804 +00a4 ourapp.exe madExcept initialization
0040b5fa +0042 ourapp.exe System 38 +0 InitUnits
0040b663 +003f ourapp.exe System 38 +0 @StartExe
00413596 +0042 ourapp.exe SysInit @InitExe
0118d338 +000c ourapp.exe Ourapp 210 +0 initialization
7752efaa +0010 KERNEL32.dll BaseThreadInitThunk