I have some logging code where there are two independent options: 1) it can
be run in the main thread or in a separate thread. 2) It can either do all
processing within the application or transfer information to an external
application via COM.
If the application runs in the separate thread/external app case for a while
(say at least 10 minutes from the first to the last log event), it does not
shut down properly and you have to kill the process. If you pause the
application in the debugger (when it does not shut down as it should), it
always brings up the CPU window on ntdll.KiFastSystemCallRet. If you run a
shorter time, OR do the logging in the main thread, OR run without the
external application/COM, it shuts down as it should in all cases.
Does anyone have a clue what the problem is?
Thanks
Magnus Oskarsson
