Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
I'm investigating memory leaks and OOM-exceptions. Now I bumped into some byte arrays which are located in the LOH (I even verified that through WinDbg). However, if I follow the root path some objects are also marked as "located in LOH" even though I think they shouldn't be (and they are also not shown in LOH in WinDbg). Could anyone clarify this for me?
- Posts: 1028
- Joined: Wed Mar 02, 2005 7:53 pm
There's no known problems with the identification of large instances in .NET Memory Profiler. Do you have any additional information about this? What type of instances do you seen in the LOH? What version of the .NET runtime and .NET Memory Profiler are you using?
SciTech Software AB
I'm not able to reproduce the issue so far... The instances are of my own types. I'm using .net 3.5 (SP and patches applied) and .NET Memory Profiler v18.104.22.168 on a Win7 machine.
Let's forget about the issue for now. As soon as I face the issue again I'll get back to you.
Users browsing this forum: No registered users and 24 guests