Re: "stop debugging" versus OnOK
- From: runcyclexcski@xxxxxxxxx
- Date: 25 Nov 2006 22:07:33 -0800
Alexander Grigoriev wrote:
This means the driver you're using (video capture?) is not handilng IRP
cancellation correctly. I'd advise to change your hardware provider or have
them fix the driver.
Alexander - do you mean that after the hard kill the buffer does get
cleaned up by SDK, but the video hardware still tries to write to the
memory? How nice. I do close the connection with the video hardware in
a soft kill. But the sofkill is not always possible (my app hangs here
and there, for other reasons). I found that a hard kill (Stop debuggin)
while the video is being written in the memory causes a blue screen
with a 100% certainty. Takes a minute. Takes longer if the frame size
in the video gets smaller.
.
- Follow-Ups:
- Re: "stop debugging" versus OnOK
- From: Alexander Grigoriev
- Re: "stop debugging" versus OnOK
- References:
- "stop debugging" versus OnOK
- From: runcyclexcski
- Re: "stop debugging" versus OnOK
- From: Alex Blekhman
- Re: "stop debugging" versus OnOK
- From: runcyclexcski
- Re: "stop debugging" versus OnOK
- From: runcyclexcski
- Re: "stop debugging" versus OnOK
- From: Alexander Grigoriev
- "stop debugging" versus OnOK
- Prev by Date: CWinApp::OnFileOpen never gets called?!
- Next by Date: Re: CWinApp::OnFileOpen never gets called?!
- Previous by thread: Re: "stop debugging" versus OnOK
- Next by thread: Re: "stop debugging" versus OnOK
- Index(es):
Relevant Pages
|