Memory Profiling
Uniwares_AS
Posts: 168
I am absolutely unable to memory profile my test application. Occasonally the Snapshot actually works and gets me some result, most of the times it just stays "Taking Snapshot" and never completes. When the application quits, ANTS reports that the application ended while sending data and that profiling will stop.
Another thing: is there any possibility to see in which LINE an object was allocated instead of only the method?
Another thing: is there any possibility to see in which LINE an object was allocated instead of only the method?
Comments
I don't believe Profiler is capable of showing the line number where an object had been allocated, but at least you can click the object in the all objects panel and see the source code for the allocation method in the source code view and be able to work it out. Maybe we can enhance this in the future.
Perfmon shows a peak of 7.6 for %time spent in GC.
If it helps, I could send the app over for testing to you.
I am probably too spoiled from C++ Profilers where the whole call stack of the allocation location is shown. In my case I see only that most of the objects are allocated in System.Collections...whatever...Resize(). thats absolutely not very helpful.
If you could create a 'logs' folder in the ANTS Profiler 3 folder, then profile the application again, a log should be created in that folder. Much appreciated if you can send the log files!
In the View menu I have
Back
Forward
Summary
All Methods
Start Page
Source Code
Hierarchy
Results
Thats it. Not finding anywhere a Call Stack view.