JDK-8169204 : Need to document JSObject Call and setSlot APIs to use weak references
- Type: Bug
- Component: javafx
- Sub-Component: web
- Affected Version: 8u102,9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-11-03
- Updated: 2020-01-31
- Resolved: 2016-11-05
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u131Fixed  |
9Fixed |
Related Reports
|
Cloners :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
In order to fix JDK-8089681 we now use weak references in the WebKit JavaScript bridge code to hold onto Java objects that are bound to JavaScript objects using JSObject.setMember. The above behaviour need to updated for other JSObject APIs like "call" and "setSlot" also in order to address JDK-8168625 Applications that rely on the previous, buggy behavior might be surprised by the fact that objects that are not strongly held by the application are subject to garbage collection even though they are bound to a JavaScript object. We should document this fact in the WebEngine documentation in the section on "Calling back to Java from JavaScript".
Comments
|