Skip to content

OOME when opening CPU samples in JFR #622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pflaska opened this issue Jan 31, 2025 · 1 comment
Closed

OOME when opening CPU samples in JFR #622

pflaska opened this issue Jan 31, 2025 · 1 comment
Assignees
Labels

Comments

@pflaska
Copy link

pflaska commented Jan 31, 2025

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps:

  1. Load a JFR file (My JFR is ~250MB).
  2. Switch to Samper
  3. Click the CPU button to get CPU samples
  4. Error in console.

Current behavior:

java.lang.OutOfMemoryError: Java heap space
Dumping heap to /home/pflaska/.visualvm/2.1.10/var/log/heapdump.hprof ...

Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "AWT-XAWT"
Heap dump file created [1504753334 bytes in 7,055 secs]

Expected behavior

The JFR is not huge, VisualVM should be able to open it.

** Workaround**
Increasing -Xmx to 8GB works.

Desktop (please complete the following information):

  • Ubuntu 22.04.5 LTS \n \l
  • Java(TM) SE Runtime Environment 17-ea+15-LTS-1230
  • 2.1.10
@pflaska pflaska added the bug label Jan 31, 2025
@thurka thurka self-assigned this Jan 31, 2025
thurka added a commit that referenced this issue Feb 7, 2025
@thurka
Copy link
Member

thurka commented Feb 7, 2025

Memory usage improved. With the above fix I was able to open test jfr file with 1500M Xmx, while originaly VisualVM needs around 6G.

@thurka thurka closed this as completed Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants