JDK-8102138 : WebView needs to be MT safe based on fix for RT-15195
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: web
  • Affected Version: 7u6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-08-01
  • Updated: 2015-06-16
  • Resolved: 2012-09-20
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.
JDK 8
8Fixed
Related Reports
Blocks :  
Blocks :  
Relates :  
Description
The fix for RT-15195 assumes that all pulse listeners are called on the FX thread but not during the synchronization lock held with the render thread. WebView or the patch needs to be updated to work correctly.
Comments
changesets: http://jfxsrc.us.oracle.com/javafx/8.0/scrum/graphics/webnode/rev/7e959b87ef9e http://jfxsrc.us.oracle.com/javafx/8.0/scrum/graphics/rt-closed/rev/e0e95ae3d29e
24-09-2012

done: http://javaweb.us.oracle.com/jcg/fx-webrevs/RT-23842/2
14-09-2012

Could you add some assertion to check that we have no more than 2 frames at any moment?
14-09-2012

Peter, I think we're better to address this general issue and close RT-24010 as a particular case. Here's the webrev: http://javaweb.us.oracle.com/jcg/fx-webrevs/RT-23842/1 A call to WebPage.updateContent on Event thread produces a render queue which is composed to a "render frame". The composed frame is queued for further rendering on Render thread. The queue of frames is accessed concurrently in a "wait-free" manner. This is the only shared resource that became thread-unsafe due to the changes to FX threading model.
12-09-2012

Anton, do we need anything beyond RT-24010 to resolve this one?
12-09-2012

Bump priority to Major.
06-08-2012