Re: "stop debugging" versus OnOK
- From: runcyclexcski@xxxxxxxxx
- Date: 25 Nov 2006 19:42:47 -0800
these threads that are hangning in the memory after the app is closed
are really killing me. Since the threads handle big chunks of memory
(they handle streaming video) and involve while loops, they eat up the
memory really quick. After the last blue screen, I got winerror.h and
winbase.h corrupted (crap written in wrandom places). So, each
"debugging" iteration of this application takes half an hour, and the
RAM and the HD space gets more and more corrupted. Is there a less
painful, less self-destruictive, way to debug threads?
.
- 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
- "stop debugging" versus OnOK
- Prev by Date: Re: "stop debugging" versus OnOK
- Next by Date: How can all of IE7's toolbar be translucent?
- Previous by thread: Re: "stop debugging" versus OnOK
- Next by thread: Re: "stop debugging" versus OnOK
- Index(es):
Relevant Pages
|