You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently it's possible to receive heap dumps on out of memory (OOM) but this is not yet possible for JFR. OpenJDK has this feature and we should try to implement it as well in Native Image. One of JFR's primary goals is to provide insight in the event of a crash like OOME.
Describe the solution you'd like.
The JFR implementation in Native Image should support emergency dumping like in OpenJDK.
Describe who do you think will benefit the most.
GraalVM users would be most likely to benefit. Heap dumps are probably the most important report in the event of OOM, but insights from JFR could also be very beneficial. For example, JFR's CPU and allocation profiling can help locate where problem areas are occurring. JFR's garbage collection events and thread data could also be helpful with diagnosing problems.
Describe alternatives you've considered.
There isn't much of an alternative other than leaving this feature unimplemented.
Express whether you'd like to help contributing this feature
I can help contribute this.
Feature request
Please include the following information:
Is your feature request related to a problem? Please describe.
Currently it's possible to receive heap dumps on out of memory (OOM) but this is not yet possible for JFR. OpenJDK has this feature and we should try to implement it as well in Native Image. One of JFR's primary goals is to provide insight in the event of a crash like OOME.
Describe the solution you'd like.
The JFR implementation in Native Image should support emergency dumping like in OpenJDK.
Describe who do you think will benefit the most.
GraalVM users would be most likely to benefit. Heap dumps are probably the most important report in the event of OOM, but insights from JFR could also be very beneficial. For example, JFR's CPU and allocation profiling can help locate where problem areas are occurring. JFR's garbage collection events and thread data could also be helpful with diagnosing problems.
Describe alternatives you've considered.
There isn't much of an alternative other than leaving this feature unimplemented.
Express whether you'd like to help contributing this feature
I can help contribute this.
Update #5410 when completed
The text was updated successfully, but these errors were encountered: