JDK-6718235 : Regression test for 6670162 failing on Firefox 3
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2008-06-24
  • Updated: 2010-04-04
  • Resolved: 2008-06-25
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 6
6u10Resolved
Related Reports
Relates :  
Description
Verification of the test case for 6670162 is failing on the Firefox 3 browser. This may indicate a recent and severe regression in LiveConnect functionality that may break real-world applets. It must be investigated immediately and the scope of the failure determined.
The test case fails intermittently in Internet Explorer as well, apparently in cold start situations where the JVM running the applet takes a long time to start up. This indicates a race condition in LiveConnect initialization which should not be present -- the first call from JavaScript to Java should block waiting for the applet to either successfully start or to produce an error during initialization.

Comments
EVALUATION There was a race condition in the test case for 6670162 that was causing the intermittent failures on IE. If Java cold started, causing the launch of the applet to take a long time, the initial JavaScript-to-Java call would come in between the calls to applet.init() and applet.start(), causing the test to fail because it checks the width and height at the point where both methods are executed. If start() hasn't been called yet, the width and height in the start() method will both be zero and the test will fail. This was corrected by changing the applet to call back the web page upon becoming visible to check its status and report its result. This fix to the test case also makes the test case run correctly on Firefox 3. It appears there is a race condition in the Firefox 3 browser upon the first JavaScript-to-Java call against an initially-hidden applet. Mozilla bug 441815 has been filed to track this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=441815 . Since this is not a bug in the Java Plug-In, closing as "Not a Defect".
25-06-2008