Closed
Bug 530479
Opened 15 years ago
Closed 14 years ago
firefox closes when its not supposed to
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: vshilov, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-2-25])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Every time a firefox tab is closed or a window that has nothing to do with firefox is closed there is a small chance that the whole browser would close. When this happens there is no error message. When the firefox is restarted the tabs are not recovered. This bug is annoying.
Reproducible: Couldn't Reproduce
Steps to Reproduce:
1. Close a tab or some other window
2.
3.
Actual Results:
Firefox closes sometimes
Expected Results:
Firefox should stay open
![]() |
||
Updated•15 years ago
|
Component: Shell Integration → Tabbed Browser
QA Contact: shell.integration → tabbed.browser
Comment 1•15 years ago
|
||
How often you can reproduce this issue? Would you be able to create a screencast? You can use a tool like Jing: http://www.jingproject.com/
Comment 2•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 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-2-25]
Comment 3•14 years ago
|
||
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•