Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: 9
Affects Version/s: 8u102, 9
Component/s: javafx
Labels:

Subcomponent:
web

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8169292	8u152	Murali Billa	P3	Resolved	Fixed	b01
JDK-8171877	8u131	Murali Billa	P3	Resolved	Fixed	b01

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".

backported by

JDK-8169292 Need to document JSObject Call and setSlot APIs to use weak references

Resolved

JDK-8171877 Need to document JSObject Call and setSlot APIs to use weak references

Resolved

clones

JDK-8154127 Need to document that JavaScript to Java bindings use weak references

Resolved

relates to

JDK-8089681 WebView leaks memory when containing object acts as javascript callback handler

Resolved

JDK-8168625 Java WebView communication between java and javascript fails in Java 8 U112

Closed

JDK-8171401 Release Note: Fixed memory leak when Java objects are passed into JavaScript

Closed

JDK-8169341 Broken JavaScript-to-Java callback in WebEngine with 2nd call

Open

(2 relates to)

Assignee:: Murali Billa

Reporter:: Murali Billa

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2016-11-03 11:18

Updated:: 2020-01-31 14:00

Resolved:: 2016-11-05 09:27

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates