Open
Bug 628780
Opened 14 years ago
Updated 13 years ago
Closes without warning.
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: bobfairmead, Unassigned)
References
Details
(Whiteboard: [Halloween2011Bug])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
Build Identifier:
I use Sea Monkey. I am disturbed that clicking X at any window, when I have many opened windows just closes the lot. Surely there should be some warning. I only want to close one window, not all of them. Warn me, and offer me options. So often I close everything. Annoying.
Best P.
Reproducible: Always
Updated•14 years ago
|
Component: Event Handling → General
Product: Core → SeaMonkey
QA Contact: events → general
Comment 1•14 years ago
|
||
Go to Edit-> Preferences-> Tabbed Browsing
In the "Tab Display" section is "warn me when closing a window with multiple tabs" checked?
Reporter | ||
Comment 2•14 years ago
|
||
Thanks for the reply.
But, I have that choice checked, and it still closes evrything without warning.
Bob.
Comment 3•14 years ago
|
||
Does it happen in safe mode?
<http://kb.mozillazine.org/Safe_mode#Windows>
Not sure that is Seamonkey problem, I've also faced this issue, when Seamonkey hangs for any reason and you closes one window neither with X or right click menu on system taskbar, after Seamonkey unfreeze it closes "choosed" window, but after a couple of seconds all Seamonkey windows closes without any prompt. Checked system options, saw that I have Error Reporting disabled, reenable it and try to catch such situation again
Manage to reproduce this, issue still here at least with 2.4.1, moved to 2.7a1 and will continue investigation, but don't think that things are changed.
Steps to reproduce:
0) We need freezing browser, as I have (bug 608954, will be updated later today with new data)
1) In moment of freeze, fast use right click on window on taskbar, popup-ed menu must contain active only "Close" and "Restore" items, if not either you don't be fast, or freeze was too short.
2) Select "Close" item
Expected Results:
Only one selected window will close
Actual Results:
After a couple of seconds, when browser unfreezes, it completely shuts down without any warning, notice, no breakpad window, no windows error reporting or Dr. Watson, etc.
Additional info:
Last run was under Windbg, when process go away, debugger only reports
-------------------------------------------------
ERROR: ContinueEvent failed, NTSTATUS 0xC000000D
This usually indicates that the debuggee has been
killed out from underneath the debugger.
-------------------------------------------------
so he also doesn't help to reveal whats happening here.
Build identifier: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110928 Firefox/7.0.1 SeaMonkey/2.4.1
Updated•13 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•13 years ago
|
||
Phoenix, bobfairmead,
1) Does this still happen in current builds?
2) Does it happen in Safe Mode (see comment #3)?
Whiteboard: [Halloween2011Bug][CLOSEME 2012-01-01 INCO] → [Halloween2011Bug][CLOSEME 2012-02-15 INCO]
It is hard to put Seamonkey in such conditions in Safe mode, but I'll try in a week or so, when back to work. Also, I suppose Firefox must also be affected, but it need to spend huge amount of time to reproduce...
Still happens in current builds in "normal" mode, but still don't have time to reproduce this in safe mode or firefox...
Whiteboard: [Halloween2011Bug][CLOSEME 2012-02-15 INCO] → [Halloween2011Bug]
Reproduced in FF, this happens when browser hangs during long cycle collection, I'll fill separate bug for it later
You need to log in
before you can comment on or make changes to this bug.
Description
•