"stop debugging" versus OnOK

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: runcyclexcski@xxxxxxxxx
Date: 24 Nov 2006 18:59:07 -0800

Does OnOK get called when "stop debugging" is clicked in .NET?

I've never seen any memory leaks in my program until I started creating
threads. Turns out, clicking "stop debugging" does not kill threads
that I irresponsibly did not close. This ultimately lead to multiple
BSODs in my case.

So I started killing my program softly, by first cleaning up the memory
and closing all threads within OnOK first. But now I get "memory leaks"
complaints that I've never seen with "stop debugging".

.

Follow-Ups:
- Re: "stop debugging" versus OnOK
  - From: Alex Blekhman

Prev by Date: iLike for iTunes is cool , but how they did it?
Next by Date: inline assemble in vc
Previous by thread: iLike for iTunes is cool , but how they did it?
Next by thread: Re: "stop debugging" versus OnOK
Index(es):
- Date
- Thread

Relevant Pages

Re: "stop debugging" versus OnOK
... I've never seen any memory leaks in my program until I started creating ... clicking "stop debugging" does not kill threads ... What is your development environment? ...
(microsoft.public.vc.language)
Re: Detecting and Isolating Memory Leaks Using VC6
... If you DLL is linked with static version of CRT library, ... between subsequent debugging sessions. ... > memory leaks will show up, but I got some comiler errors: ... Include this line into stdafx.h, _before_ ATL headers: ...
(microsoft.public.vc.debugger)
Re: "stop debugging" versus OnOK
... It's an MFC. ... "stop debugging" does not take care of cleanup. ... I've never seen any memory leaks in my program until I ...
(microsoft.public.vc.language)
Re: Update 2 available
... "Tom" wrote in message ... > So far it seems stable, but still has memory leaks when debugging. ... The readme file on the Borland website doesn't have a list of fixed bugs. ...
(borland.public.delphi.non-technical)