Re: Memory increasing even when in debug-break
- From: jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]")
- Date: Wed, 21 Mar 2007 09:42:02 GMT
Hi John,
Thanks for your feedback!
First, I do not think the bug documented by the KB is the same as yours.
Because the KB says that this problem only exists if Mscoree.dll and
Corperfmonext.dll are loaded and unloaded repeatedly in your application's
process, which is not true for your scenario. Additionally, what you are
experiencing is a memory leak which is not the same symptom as handle
leak(although it may introduce some type of memory increasing in certain
situation). To further ensure if your problematic .Net1.1 application is
experiencing the handle leak, you may explicit add "Handle Count" column in
the Task Manager and monitor this column to see if it increases from time
to time.
Have you tried to use the "Private Bytes" and ".NET # of Bytes in all
Heaps" to identify if the .Net1.1 leak is a managed one or unmanaged one?
If it is a native leak, we normally use DebugDiag tool to further
troubleshoot the root cause. The link below contains a training sample:
http://blogs.msdn.com/debugdiag/archive/2006/03/28/563113.aspx
Additionally, can you reproduce this issue in a little sample project? It
would be helpful to reproduce this locally so that I give it a local
debugging. Also, the 2 KBs below talk about another 2 memory leak problems
in .Net1.1:
"FIX: A memory leak may occur when COM objects are passed as VARIANT in the
Microsoft .NET Framework 1.1"
http://support.microsoft.com/kb/839047
"FIX: A memory leak may occur, and Visual Studio .NET 2003 may unexpectedly
close and then restart when you compile a large solution that contains more
than 65 projects"
http://support.microsoft.com/kb/909766
Hope this helps.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- Memory increasing even when in debug-break
- From: John Wood
- RE: Memory increasing even when in debug-break
- From: "Jeffrey Tan[MSFT]"
- Re: Memory increasing even when in debug-break
- From: John Wood
- Re: Memory increasing even when in debug-break
- From: "Jeffrey Tan[MSFT]"
- Re: Memory increasing even when in debug-break
- From: John Wood
- Re: Memory increasing even when in debug-break
- From: "Jeffrey Tan[MSFT]"
- Re: Memory increasing even when in debug-break
- From: John Wood
- Memory increasing even when in debug-break
- Prev by Date: Re: VS2005 - exceptions thrown whilst debugging
- Next by Date: Re: Can I debug in Visual Studio 2005 using old fashioned ASP
- Previous by thread: Re: Memory increasing even when in debug-break
- Next by thread: VB6 like watch window when doing unmanages debugging
- Index(es):
Relevant Pages
|
Loading