Closed Bug 521470 Opened 15 years ago Closed 13 years ago

Segfault when closing the window or tab of MyBrute.com

Categories

(Firefox :: General, defect)

3.5 Branch
x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: ranguvar, Unassigned)

References

()

Details

(Keywords: crash, Whiteboard: [CLOSEME 2011-05-30])

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20091009 Shiretoko/3.5.3
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.3) Gecko/20091009 Shiretoko/3.5.3

If one goes to MyBrute.com and then closes the tab or window, Firefox has a segmentation fault.  This is extremely repeatable, every time.

Set to Critical because the description of Critical includes "software crashes", and this may cause lost data.

Reproducible: Always

Steps to Reproduce:
1. Open www.mybrute.com in Firefox.
2. Close that tab or window.
Actual Results:  
Firefox immediately segfaults and dies completely.

Expected Results:  
The tab/window is closed as requested.

about:buildconfig -- http://pastebin.com/f6918a72f
Terminal output -- "Segmentation fault" (no other lines)
Other people with this problem -- http://bbs.archlinux.org/viewtopic.php?id=81718
That forum link needs you to be logged in, as it's in Arch's "Off Topic" section.  I just tried to provide a backtrace, but I can't seem to get a useful one, so someone else will have to.
Version: unspecified → 3.5 Branch
If you go to about:crashes in your addressbar, are there any numbers? Please post them here. Also, please ensure you have the latest flash, quicktime, java, reader, etc. And then please try to reproduce in a new Firefox profile. http://support.mozilla.com/en-US/kb/Managing+profiles?s=profile
Keywords: crash
Apologies, I tried testing with a new profile and the problem did not present itself.  I should have made sure it wasn't a plugin/extension problem first.  But now, I can't even reproduce with my normal profile, everything enabled.

Others reported they had this problem too, though, so I'm going to ask them to jump into this bug report.
Hi, has this reoccured?
Reporter, are you still seeing this issue with Firefox 4.0.1 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-05-30]
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.