Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8174777 | 8u92 | Owen Stuart | P3 | Closed | Delivered |
Applications which rely on the previously unspecified behavior might be affected by the updated behavior if the application does not hold a strong reference to an object passed to JavaScript. In such case, the Java object might be garbage collected prematurely. The solution is to modify the application to hold a strong reference in Java code for objects that should remain live after being passed into JavaScript.
- backported by
-
JDK-8174777 Release Note: Fixed memory leak when Java objects are passed into JavaScript
-
- Closed
-
- relates to
-
JDK-8154127 Need to document that JavaScript to Java bindings use weak references
-
- Resolved
-
-
JDK-8169204 Need to document JSObject Call and setSlot APIs to use weak references
-
- Resolved
-
-
JDK-8168625 Java WebView communication between java and javascript fails in Java 8 U112
-
- Closed
-
-
JDK-8170085 Javafx Webengine JSObect members working inconsistently
-
- Closed
-
-
JDK-8089776 WebView memory leak when JavaScript callbacks are assigned.
-
- Closed
-
-
JDK-8165302 Upcall from JavaScript to Java is broken
-
- Closed
-