Loading...

XML

Word

Printable

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

Subcomponent:
web

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8160576	8u112	Murali Billa	P3	Resolved	Fixed	b02

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.

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-8160576 Need to document that JavaScript to Java bindings use weak references

Resolved

is cloned by

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

Resolved

relates to

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

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-8165302 Upcall from JavaScript to Java is broken

Closed

JDK-8178878 [WebView] Java method not getting called from HTML

Closed

(3 relates to)

Assignee:: Murali Billa

Reporter:: Kevin Rushforth

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2016-04-12 19:03

Updated:: 2020-01-31 14:00

Resolved:: 2016-06-29 10:24

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates