Closed
Bug 431178
Opened 17 years ago
Closed 17 years ago
Firefox 3b5 crashes when you access applet property before window.onload fires
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 405357
People
(Reporter: gerds21, Unassigned)
References
Details
(Keywords: crash, testcase)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
This seems to be a LiveConnect problem on Windows XP (SP2) for Firefox 3 beta5.
If I have an applet on a page, and I try to use javascript to interact with the applet BEFORE window.onload has fired, then the browser crashes.
AFTER window.onload has fired, everything is ok.
Reproducible: Always
Steps to Reproduce:
1. Load a web page with a java applet. Javascript code interacts with applet before window.onload
2. Firefox 3 beta 5 crashes.
3.
Actual Results:
Crash
Expected Results:
All other browsers behave as they should.
I will include several test cases to prove my point.
What is even stranger is that you don't even need to access a defined applet property.
If I try to access any random undefined applet property before window.onload has fired, I get a crash. For example,
var dummy = document.getElementById('applet').shdhfjhsjd6768
would crash the browser.
Reporter | ||
Comment 1•17 years ago
|
||
This test page crashes for me with Sun Java 6, FireFox 3 beta5.
The page should reveal the Java version by querying the applet.
FireFox 2 and Internet Explorer show the Java version correctly.
I realize that often one waits for window.onload to fire before interacting with the applet, but still there should not be a crash.
My experiments show that newer versions of Sun Java (> 1.4.2) do not require one to wait for window.onload before one can interact with the applet.
Reporter | ||
Comment 2•17 years ago
|
||
Reporter | ||
Comment 3•17 years ago
|
||
Comment 4•17 years ago
|
||
This seems a duplicate of Bug 430846. It regressed around the same time. Eric, can you dupe yourself to this bug (or to Bug 405357) if you think that the problem is similar?
Keywords: hang
Version: unspecified → Trunk
Updated•17 years ago
|
Reporter | ||
Comment 5•17 years ago
|
||
I will add my comments to Bug 405357, since there does appears to be overlap here. Thanks!
Comment 6•17 years ago
|
||
Hi Eric, thanks for your testcases.
Based on the Crash Stack Data i got when testing this testcases (http://crash-stats.mozilla.com/report/index/c0cf202e-1ba9-11dd-b931-001cc45a2ce4 and http://crash-stats.mozilla.com/report/index/5d694deb-1baa-11dd-92d1-001cc45a2c28) i dupe this bug to bug 405357.
Also this crash is fixed for me with the Tryserver Build from jst https://build.mozilla.org/tryserver-builds/2008-05-05_16:35-jst@mozilla.com-plugin-fun/
You need to log in
before you can comment on or make changes to this bug.
Description
•