.NET Mem profiler doesn't track these memory allocations.
I've tried using LeakDiag from Microsoft to find the leak but the stack it gives me is truncated so I can't see where my software calls come from. I think the stack truncation has to do with frame stack omission used by Microsoft when they compile the .NET framework dlls.
Anyway, the leak is driving me nuts and I can't find where it's originating from.
Itâ€™s possible that this memory is used by unmanaged resources wrapped in managed classes. Unfortunately, the current version of the profiler does not present unmanaged resources used by the profiled process. Weâ€™re currently looking into the possibilities of adding an unmanaged resource tracker to the profiler. If you believe that this tracker is an important feature, you can tell us by using our poll at http://memprofiler.com/featurerequest.aspx.
Anyway, you can use .NET Memory Profiler to try to locate instances that may wrap your Win32 heaps memory. The dispose tracker is useful for this.
SciTech Software AB
Users browsing this forum: Bing [Bot], Google [Bot] and 15 guests