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
Oracle looked into the report and created an additional bug report, that describes the root cause for this issue and suggests a solution:
Root cause
The callback is eligible for garbage collection after the setter returns, since there are no strong references to it. It is possible (or likely) that the callback is freed before it is called, and the call will jump through a dangling pointer instead, which would likely cause a crash.
Solution
Replace the use of an implicit memory session with a shared session and allocate the memory for a callback (aka setting the pointer to a function that is executed as the callback) in the shared session.
Please agree to the following
Summary
JVM crashes on executing callback
What software is involved?
Steps to Reproduce
apply()
method as the callback function to be executedExpected Behavior
Callback function executes
Actual Behavior
JVM crashes
Reproducibility
Always
Relevant Log Output
Anything else?
A bug report has been submitted upstream at https://bugreport.java.com/bugreport/crash.jsp
The text was updated successfully, but these errors were encountered: