DbgMsgSrc -1 saturates the DBWinReader by outputing 160.000 lines as quickly as possible.
In the last milliseconds of existance of the process the PID appears zero ? This should not be possible, because we keep the handle of the process allowing the Process-information to be captured after the process has terminated.
The behaviour is not completely reproducible, but it happens often, I would say +70% of the runs
DbgMsgSrc -1 saturates the DBWinReader by outputing 160.000 lines as quickly as possible. In the last milliseconds of existance of the process the PID appears zero ? This should not be possible, because we keep the handle of the process allowing the Process-information to be captured after the process has terminated.
The behaviour is not completely reproducible, but it happens often, I would say +70% of the runs