Closed
Bug 405641
Opened 18 years ago
Closed 17 years ago
Repeatedly clicking a button hangs or crashes Firefox
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: sjoerd-mozilla, Unassigned)
Details
(Whiteboard: closeme 2009-07-07)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b1) Gecko/2007110904 Firefox/3.0b1
By repeatedly clicking a specific form button (quickly, > 30 times), Firefox crashes and sometimes hangs.
Reproducible: Always
Steps to Reproduce:
1. Open a specific intranet webpage.
2. Click the search button repeatedly.
3. Crash.
Comment 1•18 years ago
|
||
Did the crash reporter dialog appear? Since the page is part of an intranet we won't be able to reproduce for fixing. Can a tescase be made, attach code that reproduces the bug.
Firefox hangs and Windows suggests sending this error report.
firefox.exe.hdmp also available, but too big.
References an applet, which may or may not cause this bug. The "search" button triggers the bug.
Comment 5•18 years ago
|
||
(In reply to comment #4)
> Created an attachment (id=290397) [details]
> Source of the webpage which causes the crash
>
> References an applet, which may or may not cause this bug. The "search" button
> triggers the bug.
Loading the source triggers loading Java, proceesing the source and quitting with an Exception, class not found or something like that, as you didn't supply the other files icluded in the source, <script type='text/javascript' src='org.ajax4jsf.framework.ajax.AjaxScript.faces'></script> etc.
Does this bug also occur if you disable Java?
Which version of Java do you use, does the Java console (type 5 to see all messages) show any errors?
Does it occur if you disable Javascript?
I fully understand you don't want to show the full source, and we also aren't interested in seeing the full source, minimized testcases are needed to show what triggers the bug.
If you want to make a more minimal testcase, disable js and loading of images, and if it still crashes, you can remove js and images from the source of the testcase. Outcomment some divs to see if the problem lies there, if not, backup and delete. If the bug is still seen, delete the backup, otherwise restore.
Remove all what isn't needed to show the bug.
Mostly you can include CSS and JS into your source file, but if they are needed externally to show the crash, upload external files first, the edit the mainfile to include the URL of the attachments on bugzilla, before uploading the main file. A testcase made like this can be tested by more testers, and they can reduce it further.
Validator gave me some hints:
http://validator.w3.org/check?uri=https%3A%2F%2Fbugzilla.mozilla.org%2Fattachment.cgi%3Fid%3D290397&charset=%28detect+automatically%29&doctype=Inline&group=0
Line 130, Column 64: there is no attribute "mayscript".
….unity.webuiapplet.Applet" mayscript="MAYSCRIPT" width="0" height="0" archive
...
(Remember XHTML is all lower-case)
...
Line 167, Column 106: ID "jsf_tree_64" already defined.
…type="hidden" name="jsf_tree_64" id="jsf_tree_64" value="rO0ABXNyAEdvcmcuYXBh
✉
An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).
Line 129, Column 58: ID "jsf_tree_64" first defined here.
…type="hidden" name="jsf_tree_64" id="jsf_tree_64" value="rO0ABXNyAEdvcmcuYXBh
Same for ID "jsf_state_64" and ID "jsf_viewid"
Comment 6•17 years ago
|
||
can you reproduce using FF 3.5 beta?
http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: closeme 2009-07-07
Unfortunately, I no longer have access to the webpage which caused the crash.
Comment 8•17 years ago
|
||
Well, WFM unless someone can repro.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•