471,337 Members | 802 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,337 software developers and data experts.

Bug? : Large amount of memory used while debugging.

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

Jul 22 '05 #1
2 1285
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!
***************************
"ts******@gmail.com" wrote:
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

Jul 22 '05 #2
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

Cowboy (Gregory A. Beamer) - MVP wrote:
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!
***************************
"ts******@gmail.com" wrote:
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


Jul 22 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

36 posts views Thread by Andrea Griffini | last post: by
1 post views Thread by Robert May | last post: by
6 posts views Thread by nilavya | last post: by
20 posts views Thread by Hemant Shah | last post: by
17 posts views Thread by byte8bits | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.