JDK-8133523 : _releaseObject called from wrong thread
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 7u4,8u51
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_8
  • CPU: x86
  • Submitted: 2015-08-12
  • Updated: 2017-12-26
  • Resolved: 2015-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.
JDK 7 JDK 8 JDK 9
7u91Fixed 8u101Fixed 9 b94Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
Description
FULL PRODUCT VERSION :


ADDITIONAL OS VERSION INFORMATION :
Windows 8.1

A DESCRIPTION OF THE PROBLEM :
At Mozilla we got multiple reports about Firefox crashes related to the Java plugin.

We tracked it down to the plugin calling _releaseObject (NPN_releaseobject) from a thread other than the main thread. This can race with our JS GC and cause Firefox crashes.

This affects multiple companies and intranet websites.


REPRODUCIBILITY :
This bug can be reproduced often.


Comments
Verified on Windows 7 / FF ESR 52.2.1 / 9b176 with Java Detection official applet (Open two tabs loading the same applet, close one tab, making sure the other is still running OK.)
05-07-2017

We have to take it due to P1 and PSU15_04 respin. SQE verified the fix with 8u66 b18.
16-11-2015

Mozilla bug reports mention that the issue is reproducible with 8u31 and 8u40 but the bug has label regression. Is it a mistake? If not in what release was it introduced?
06-11-2015

The fix for this also addresses another Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1221448
05-11-2015

Adjusting priority of this issue: ILW=HMH => P1
29-10-2015

Link to the bug being tracked by Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1140616
29-10-2015