Bug? : Large amount of memory used while debugging.

  • Thread starter Thread starter tstephan
  • Start date Start date
T

tstephan

I am debugging a small app that normally runs in a few MB. When
debugging the code below, my app bloats to 1GB (and more if I let it).


Assembly[] ara = AppDomain.CurrentDomain.GetAss­emblies();
foreach( Assembly a in ara )
{
System.Diagnostics.Debug.Write­Line( ">>>" + a.FullName );
System.Diagnostics.Debug.Write­Line( " " + a.CodeBase );
System.Diagnostics.Debug.Write­Line( " " + a.ToString() );
System.Diagnostics.Debug.Write­Line( " " +
a.GetName().FullName );
System.Diagnostics.Debug.Write­Line( " " + a.GetName().Name
);
System.Diagnostics.Debug.Write­Line( " " +
a.GetName().Version );



}


The key to cause the bloat to occur is to have the variable "a"
expanded in the locals window (so it's properties are visible). I
haven't tried this on a completely stripped down app, but since our app

has just been started I suspect that same would occur. Has anyone else

experienced this? Even after F5ing the memory is not released.

Thanks,
Todd
 
I am having difficulty reproing the issue with my own application. I see
about 70 MB max for one of my larger windows applications when running the
loop, even with locals open for a. Do you have a repro sample?

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
I haven't created a stripped down app yet as it only seems to appear in
that one case so far (and I am done debugging it :). I will put
together a stripped down app over the weekend and get back to you with
the results (and post the app code if it reproduces).

Thanks,
Todd
I am having difficulty reproing the issue with my own application. I see
about 70 MB max for one of my larger windows applications when running the
loop, even with locals open for a. Do you have a repro sample?

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************


[email protected] said:
I am debugging a small app that normally runs in a few MB. When
debugging the code below, my app bloats to 1GB (and more if I let it).


Assembly[] ara = AppDomain.CurrentDomain.GetAss­emblies();
foreach( Assembly a in ara )
{
System.Diagnostics.Debug.Write­Line( ">>>" + a.FullName );
System.Diagnostics.Debug.Write­Line( " " + a.CodeBase );
System.Diagnostics.Debug.Write­Line( " " + a.ToString() );
System.Diagnostics.Debug.Write­Line( " " +
a.GetName().FullName );
System.Diagnostics.Debug.Write­Line( " " + a.GetName().Name
);
System.Diagnostics.Debug.Write­Line( " " +
a.GetName().Version );



}


The key to cause the bloat to occur is to have the variable "a"
expanded in the locals window (so it's properties are visible). I
haven't tried this on a completely stripped down app, but since our app

has just been started I suspect that same would occur. Has anyone else

experienced this? Even after F5ing the memory is not released.

Thanks,
Todd
Click to expand...
Click to expand...
 
Back
Top