Re: Memory increasing even when in debug-break

Hi Jeffrey,

Thanks for the kind words -- sorry to bother you again but I do have a
couple of follow-ups if you don't mind.

While uninstalling this driver seems to have fixed the problem on .Net 2,
another test machine that is running the app under .Net 1.1 is still
exhibiting the same leak. I did some debugging and this time the callstack
showed that a call to corperfmonext.dll is very active allocating stuff. I'm
a little confused now, I'm left wondering whether this bug is even related.

I found a knowledge base article that gave me a hint, entitled "A handle
leak occurs in a process that uses Corperfmonext.dll in the .NET Framework
1.1", http://support.microsoft.com/kb/842675. Do you have any more
information on this? It does seem to suggest a leak relating to that DLL and
I'm wondering if it's the same issue I'm seeing. Few questions:

1. Is this bug related to the bug you mentioned earlier?
2. Do you know whether this bug could result in a steady increase of 20k/s
in private bytes?
3. Is this fixed in .Net 2 (and perhaps that's why I cannot see it in that
environment?)
4. Do you have a link for the hotfix?

Also, do you know of any articles that explain the reasoning behind having
to do this whole DLL injection thing for apps that query performance data...
to me it seems a bit strange, especially problematic when you're trying to
fine-tune performance of your app, not to mention the possibility of
security ramifications from having misbehaving DLLs in your process space
(eg. how do I know these DLLs don't have buffer overruns?).

Thanks again for all your help. I realize this is going outside the scope of
this group, if you'd prefer me to move the thread elsewhere I'll happily
oblige!

John


.

Relevant Pages

  • Re: .net dll call from native c++
    ... > I've got a native C++ app which calls a 3rd parth .NET DLL using the ... This works fine when the DLL is ... bug in .NET and Windows that will potentially cause a deadlock. ... LoadLibrary/GetProcAddress and the sections in the config file are used ...
    (microsoft.public.dotnet.general)
  • Re: too many consecutive exceptions
    ... i have found the bug and a workaround. ... the groupbox component. ... first the main app and second the dll. ...
    (alt.comp.lang.borland-delphi)
  • Re: .NET-BroadcastEventwindow.1.0.3300.0.9:---Application Error
    ... My app is a C# P/Invoke wrapper around a DLL. ... Running the unit tests seem to be fine. ... Windows Forms team will investigate the bug. ...
    (microsoft.public.dotnet.framework.clr)
  • Re: KB 812012 - WebClass memory leak
    ... Webclass and you call the Split function frequently. ... We identified the leak was coming from ... you can workaround this bug by using Split inside a VB dll and host ...
    (microsoft.public.vb.bugs)
  • Re: Display a message each time functions are called
    ... This app is basically an e-Learning and content ... That does not sound like a problem with client-side scripting either. ... Not a client-side script problem either, unless there was a bug in the user ... very well for reporting: ...
    (comp.lang.javascript)