Closed
Bug 484170
Opened 16 years ago
Closed 16 years ago
crash when closing last tab
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
VERIFIED
INCOMPLETE
People
(Reporter: cuttermanj, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
When only one tab is open (any url), middle clicking on it to close it closes Firefox
Reproducible: Always
Steps to Reproduce:
1.have one tab open with any url
2.middle click on the tab
Actual Results:
Firefox closes
Expected Results:
Firefox should stay open with one blank tab
I have flashblock plug-in. I have the setting "always show tab bar" on. I saw a similar bug for 3.0 branch, this bug is for 3.1b3.
Comment 1•16 years ago
|
||
Can you try in safe mode? This does not happen for me in trunk.
Version: unspecified → 3.1 Branch
Comment 2•16 years ago
|
||
Severity: normal → critical
Comment 3•16 years ago
|
||
This behaviour has changed, closing the last tab (except with the mouse) now closes the window. There is a related preference accessible from about:config -
browser.tabs.closeWindowWithLastTab
My understanding is that setting this to false will restore the behaviour you are expecting.
If you actually crash (i.e. crash reporter comes up or Windows tells you the application had a problem and needs to be closed) then please provide more details as outlined in the link in comment 2. Otherwise this is a dupe of bug 456405
Comment 4•16 years ago
|
||
This problem exists only in last version 3.0.8 !
In previous version 3.0.7 it isn't occur !
EVERYTIME when using multiple TABs... clicking the "X" to close one of all and
other still loading the FF 3.0.8 crash. :-(
Please, correct this fatal error !
Thanks.
Morais
Comment 5•16 years ago
|
||
Some crashes report:
http://crash-stats.mozilla.com/report/index/e116f850-c581-4d1c-bff0-ecbc02090406
http://crash-stats.mozilla.com/report/index/9a613ff1-5105-43bd-8fd1-bd26b2090406
http://crash-stats.mozilla.com/report/index/8b281f14-2c15-43af-a5dc-efc752090405
http://crash-stats.mozilla.com/report/index/6f417be8-c2da-4ac1-9d54-92ad12090405
and much more...
Comment 6•16 years ago
|
||
Reporter: Without more information this report is incomplete. (see comment 3)
Alexandre: This bug report has nothing to do with you. Please read:
http://quality.mozilla.org/bug-writing-guidelines
As to your posted crash reports, you have a crashing add-on:
bp-e116f850-c581-4d1c-bff0-ecbc02090406 [@ coFFPlgn.dll@0x2a9e5 ]
This is from a Norton toolbar of some kind. I suggest you disable/uninstall it. This is not a Mozilla bug; please report it to the authors of this add-on. Please seek any further help at support.mozilla.com.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
Comment 7•16 years ago
|
||
Congratulations Dave ! :-)
I don't know how do you find this information in CRASH REPORT, but it is true !!!
After I disable the "Norton Safe Web" option, FF crashes has stopped.
BUT... in previous FF version (3.0.7) this problem not occurred...
Thanks a lot.
Morais
PS: Why do you talk "Alexandre: This bug report has nothing to do with you." ?
I searched for "crash tab" and all BUGs where I post my problem was replied with similiar answer... :-(
The TITLE/SUMARY of this BUG has exactly the problem... and you help me to stop it !
Comment 8•16 years ago
|
||
(In reply to comment #7)
> I don't know how do you find this information in CRASH REPORT, but it is true
> !!!
Magic. i.e. I dumped the signature's DLL file name on the report into Google.
> PS: Why do you talk "Alexandre: This bug report has nothing to do with you." ?
This bug was on closing last tab with middle-click, and may or may not be an actual crash. Yours was a crash on closing one with others loading. Not the same issue. Your crashes were also in the 3.0 branch and this was for 3.1 beta. There's always the possibility they could be the same, but with just the information given there is not enough info to say they are. You should file new bugs in this instance instead of posting in one that may or may not be related.
Glad you fixed your issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•