Fully featured low overhead profiler for Java EE and Java SE platforms.
Ultimate profiling and monitoring solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Inspecting only newly created objects after memory mark

Moderators: Vladimir Kondratyev, Anton Katilin

Inspecting only newly created objects after memory mark

Postby i.b.dimitrov » Mon Jun 21, 2010 8:25 pm

Hello,

I'm new to your YourKit profiler and found it is a great tool. However I don't know how to accomplish a particular thing and hope you will help :-)

My question is regarding memory profiling (I'm hunting for memory leaks ;-) )
Is there any way to inspect only newly created objects after a memory mark? My questions is because the profiler reports I have some 40'000 objects of certain type but I have only 35 of them considered to be new (this is in the live view and after I run GC several times). Now if I take a memory snapshot I got a table with so many objects that I just don't know where to start. It would be very nice if I can trace allocations and root path only for them... You know I'm 100% sure they are leaked but I don't know how to find them in those large list of objects.

Do I miss something?

Best Regards,
Ivan Dimitrov
i.b.dimitrov
 
Posts: 1
Joined: Mon Jun 21, 2010 8:11 pm

Re: Inspecting only newly created objects after memory mark

Postby Tobbe » Tue Jun 22, 2010 8:19 am

Sound like a useful feature.
Tobbe
 
Posts: 72
Joined: Thu Feb 21, 2008 11:08 am

Re: Inspecting only newly created objects after memory mark

Postby Anton Katilin » Tue Jun 22, 2010 2:18 pm

Hello Ivan

You can record object allocations:
http://www.yourkit.com/docs/net50/help/allocations.jsp

You will be able to easily identify objects created after allocation recording has been started.

Best regards,
Anton
Anton Katilin
 
Posts: 5576
Joined: Wed Aug 11, 2004 8:37 am


Return to .NET Profiler

Who is online

Users browsing this forum: No registered users and 2 guests