I'm used to the "Garbage Objects" tab in YourKit.
It's available in 2024.9, but I don't see it anymore in 2025.3 when I open the same memory snapshot as in 2024.9.
I couldn't find anything related in the "What's new" section of 2025.3.
Is there a way to show it again?
Thanks!
Where is tab "Garbage Objects" in 2025.3?
-
- Posts: 1675
- Joined: Tue Aug 10, 2004 7:52 pm
Re: Where is tab "Garbage Objects" in 2025.3?
https://www.yourkit.com/docs/java-profi ... merged.jsp
Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"
Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"
-
- Posts: 4
- Joined: Fri May 23, 2025 9:01 am
Re: Where is tab "Garbage Objects" in 2025.3?
Thank you for your reply.
But unfortunately I still don't understand how to use the new interface to achieve what the GC tab did in the old version.
For example, I found this helpful to find possible hot spots I should optimize:

I don't see a way in the new UI to see the number of GCed objects, etc.
But unfortunately I still don't understand how to use the new interface to achieve what the GC tab did in the old version.
For example, I found this helpful to find possible hot spots I should optimize:

I don't see a way in the new UI to see the number of GCed objects, etc.
-
- Posts: 1675
- Joined: Tue Aug 10, 2004 7:52 pm
Re: Where is tab "Garbage Objects" in 2025.3?
Both views — the new "Allocations" view and the old "Garbage" view — are tools for identifying excessive object allocations, i.e., allocation hot spots.
Unlike the "Garbage" view, which reported the number of collected objects, the "Allocations" view shows the number of allocated objects. In the majority of cases, there is a direct correlation between object creation and collection. This is logical: if created objects are not collected, it indicates a memory leak, which will soon lead to an OutOfMemoryError (OOME).
The new "Allocations" view offers several advantages:
- It focuses directly on the task of identifying allocation hot spots.
- It is significantly faster and require less resources.
- It is available both during live sessions and in performance snapshots. You no longer need to capture a heavy memory snapshot with the entire Java heap to investigate allocation hot spots.
Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"
Unlike the "Garbage" view, which reported the number of collected objects, the "Allocations" view shows the number of allocated objects. In the majority of cases, there is a direct correlation between object creation and collection. This is logical: if created objects are not collected, it indicates a memory leak, which will soon lead to an OutOfMemoryError (OOME).
The new "Allocations" view offers several advantages:
- It focuses directly on the task of identifying allocation hot spots.
- It is significantly faster and require less resources.
- It is available both during live sessions and in performance snapshots. You no longer need to capture a heavy memory snapshot with the entire Java heap to investigate allocation hot spots.
Best regards,
Vladimir Kondratyev
YourKit GmbH
http://www.yourkit.com
"Don't get lost in data, get information!"