VisualVM Retaining sizes is stuck at 33%
@thurka is already working on this.
Since Jun 6, 2023.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I have a 6GB heap dump that I want to analyze. Basically find out where a lot of the sources of Memory Leaks come from.
When starting the determine the Dominators.
It goes through 3 progress bars.
At the third one (Computing Retained Sizes) it gets stuck instantly on 33% when GC Sizes are computed.
And while it seems to continue to work (after allocating 16GB on startup) it seems to barely use any resources.
It uses 7% of my Entire CPU to do its work.
Is this normal?
The progress bar "while improved" is basically still useless.
(I remember a time where there was no % at all)
To Reproduce
Steps to reproduce the behavior:
Start Visual VM take any Heap Dump thats like 6-10GB large and try to determine the Dominators.
Expected behavior
I guess be faster? And also progress communicated?
Like "1000/432312 Files processed"
Also maybe "performance options" that could be set to utilize system hardware a lot more?
VisualVM log
Even ran through the command line there is 0 logs besides: "Program found another console was used so it will be using the console provided"
logfile.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.