Closed
Bug 531594
Opened 16 years ago
Closed 15 years ago
restore dialog shows up after SIGTERM
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: cleanrock, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091106 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091106 Firefox/3.5.5
I have "Show my windows and tabs from last time" enabled and if i logout from X with firefox running i will get the restore dialog when starting firefox next time.
Would be nice if firefox can handle this forced exit in a cleaner way so the restore dialog dont show up.
Reproducible: Always
Steps to Reproduce:
1. open two firefox windows
2. send SIGTERM to firefox
3. start firefox
Actual Results:
restore dialog shown
Expected Results:
session restored (no restore dialog)
Comment 1•16 years ago
|
||
The process IS killed so it's not a clean exit. If you never want to see the crash dialog, set browser.sessionstore.max_resumed_crashes to a very high value or -1.
you're not actually asking about sigterm, you're asking about honoring session management. we have a bug for that.
Whiteboard: DUPEME
(In reply to comment #2)
> you're not actually asking about sigterm, you're asking about honoring session
> management. we have a bug for that.
I thought a SIGTERM is what is sent to apps when i logout from X.
Sounds promising, if i can avoid this dialog when restarting FF after i exited X with FF running im happy.
it should have been bug 93789. but i can't figure out what happened.
the general idea is that when you close your session, the system starts by sending "please save-quit" messages to apps, any apps that don't respond get kill'd.
The general feeling I'm getting on this bug is "this is expected/as-designed" and therefor not a bug.
Resolving this as INVALID. If this is in error, please reopen with your justification as to why it is a bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•