AccessViolationException after finishing debugging

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: "Judah" <Judah@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 25 Apr 2005 09:49:25 -0700

We have a smart client application built using .NET framework 2.0 betas. With
beta 1, our application worked fine. With Visual Studio 2005 beta 2, when I
start the app with debugging, all runs fine until I close the application, at
which point, the debugger tells me

-----------
System.AccessViolationException

Attempted to read or write protected memory. This is often an indication
that other memory is corrupt.

at System.Windows.Forms.UnsafeNativeMethods.IConnectionPoint.Unadvise(Int32
cookie)
at System.Windows.Forms.AxHost.ConnectionPointCookie.Disconnect()
at System.Windows.Forms.AxHost.ConnectionPointCookie.Finalize()
------------

The debugger breaks and shows some assembly code where the exception is
occurring. Oddly enough, this only happens while I'm debugging; if I run the
app without debugging, no exception occurs.

Any ideas what could be wrong?
.

Prev by Date: Re: Debugger not working in Vs.net 2003
Next by Date: Re: Debugger not working in Vs.net 2003
Previous by thread: VS.Net 2002 Crashes while debugging
Next by thread: VS.NET 2003 Debug Problem in IIS
Index(es):
- Date
- Thread

Relevant Pages

Searching for Exception tracker engine
... During debugging there is many times that I get Exception and tracking the ... error and finding origin (unit/line) code is useful. ... name) engine that when I included that with my app it reports unit/line ... Is there any lib that I include with app to detect exception errors line no ...
(borland.public.delphi.ide)
Re: Mixed assembly crashes on exit
... main project to mixed, and also set debugging for the ... a kind of stack corruption problem. ... It will not necessarily help (since the app is mixed, not pure native), but still ...
(microsoft.public.vsnet.debugging)
Re: Tcl crashes
... If you can get Tcl, Tk, Itcl and whatever extensions you used compiled ... Tcl has some memory debugging ... It is expensive and slows down execution of the app substantially. ... the app always crashes under windows. ...
(comp.lang.tcl)
Re: .NET application Shell Componentization problem.
... I guess you only tried debugging the app? ... Then you will know whether the app is even getting started properly or not. ... Create a new image with Explorer shell and see if you can work with your app there. ... Is you custom shell image Minlogon or Winlogon based? ...
(microsoft.public.windowsxp.embedded)
Re: VS2005 and CF3.5 not working ?
... I remember on the desktop that net 1.1 app did run on a machine with only ... .NET Framework that is not supported by the debugger. ... The debugger has made an incorrect assumption about the Microsoft ... The Microsoft .NET Framework version specified by you for debugging ...
(microsoft.public.dotnet.framework.compactframework)