Examine .Net Memory Leaks

re: Examine .Net Memory Leaks

a reader — Tue, 15 Apr 2008 18:54:13 GMT

FileSystemWatcher has a Dispose method that should be called to release unmanaged resources. The dispose method can optionally release managed resources as well.

re: Examine .Net Memory Leaks

Doug Kimzey — Thu, 17 Apr 2008 22:22:58 GMT

Thank you for the really timely info. I am currently tracking down a memory leak in an OCX being called from a VFP 9 application. This OCX returns data to the VFP application as BSTRs through CString::AllocSysString(). Would you know if VFP handles the cleanup of BSTRs allocated in an OCX and are there any VFP calls that will invoke garbage collection to handle these BSTRs?

Thanks again,

Doug Kimzey

Senior Developer

DPRA, Inc.

.NET Tools maturing

Greg — Tue, 22 Apr 2008 01:57:57 GMT

Good to see Visual Studio 2008 making progress in adding development tools lacking in VS2003 and VS2005 (memory debugging, profiling, etc.).

It would still be nice to get the profiler built into VS 2008 pro instead of just team foundation.

re: Examine .Net Memory Leaks

Calvin_Hsia — Tue, 22 Apr 2008 03:04:20 GMT

Doug: VFP Garbage collection is limited to names in the name table, not BSTRs allocated in an OCX

Such BSTRs should follow COM Allocation rules:

http://msdn2.microsoft.com/en-us/library/ms686638(VS.85).aspx

x86 64 run command not found

x86 64 run command not found — Fri, 30 May 2008 18:57:15 GMT

PingBack from http://jarrett.thedigestabout.info/x8664runcommandnotfound.html

Synchronize your files across machines with Mesh

Calvin Hsia's WebLog — Wed, 24 Sep 2008 05:08:37 GMT

I have a collection of almost 30,000 pictures and videos. When I add new pictures to the collection,

Overload Operator new to detect memory leaks

Calvin Hsia's WebLog — Tue, 20 Jan 2009 05:48:50 GMT

There are various leak detection methods for memory allocators. A popular one is to tag each allocation

Memory Leaks Demo & Detection in .NET Application

Bill Li — Wed, 11 Feb 2009 07:36:10 GMT

Memory leaks are always headache of developers. Do .NET developers no longer bother to worry about memory