Cancel/Stop/Abort HeapDump operations like GC Roots or Retained Size
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
Accidentally clicking on GC root or Retained Size will start a Heap-Global computation possibly taking hours on large heaps.
Describe the solution you'd like
It would help to be able to cancel such an operation.
Describe alternatives you've considered
Restarting VisualVM / Re-Loading the Heap also takes a lot of time
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.
Research direction
The issue names HeapDump operations such as GC Roots and Retained Size but gives no files, tests, or entry points. Start by locating those operations and documenting how long-running computations are launched; done means an in-progress operation can be cancelled without restarting VisualVM or reloading the heap.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100