After I force quit because memory usage, it opens all the same windows on reopen

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
6 years ago
6 years ago

People

(Reporter: Chris Babcock, Unassigned)

Tracking

8 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Build ID: 20111104165243

Steps to reproduce:

I had to force quit from buffer overflow or something, memory was near 400 MB of ram. 


Actual results:

When I reopen Firefox it opens all the windows that caused the problems!  Really?  I would think the same problem would happen if someone went on to a site, and it crashed my browser, it reopen to the same place with the same security risk. How does that make sense? 


Expected results:

It should have prompted me to ask if I should want to restore or open a new browser.  It used to.  This is a security problem as well as irritating.
This is by design to restore your tabs/windows on crash, even if self-induced by a 'forced' shutdown of the Browser. 

Yes, restarting will indeed reload the suspect bad/problem causing tab and could lead you to forcing it down again.  Some cases you can select the tab and close it before it has a change to hang the browser.  

400mb of ram usage is NOT abnormal, and should not be a cause to force shutdown. Unless the bad-behaving tab is chewing up memory/cpu rapidly, then you may have to resort to a forced shutdown. 

After the 2nd 'forced shutdown' you are, or should be presented with a Session Restore page listing your open tabs.  If you know the tab that was causing the problem you can 'Uncheck' that tab from loading and the browser will start normally once you click Restore, or from that screen you choose to just afresh. 

The number of crashes is controlled by a pref in about:config

browser.sessionstore.max_resumed_crashes

Setting this to '0' (zero) will present the Session Restore screen after your 1st 'forced shutdown' if you so desire. 

Closing this as WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 2

6 years ago
Hi Jim,

I think this should be the default behavior.  Why not?  What are you gaining by allowing a restart with a prompt first?  Just something to think about.

Chris

(In reply to Jim Jeffery not reading bug-mail 1/2/11 from comment #1)
> This is by design to restore your tabs/windows on crash, even if
> self-induced by a 'forced' shutdown of the Browser. 
> 
> Yes, restarting will indeed reload the suspect bad/problem causing tab and
> could lead you to forcing it down again.  Some cases you can select the tab
> and close it before it has a change to hang the browser.  
> 
> 400mb of ram usage is NOT abnormal, and should not be a cause to force
> shutdown. Unless the bad-behaving tab is chewing up memory/cpu rapidly, then
> you may have to resort to a forced shutdown. 
> 
> After the 2nd 'forced shutdown' you are, or should be presented with a
> Session Restore page listing your open tabs.  If you know the tab that was
> causing the problem you can 'Uncheck' that tab from loading and the browser
> will start normally once you click Restore, or from that screen you choose
> to just afresh. 
> 
> The number of crashes is controlled by a pref in about:config
> 
> browser.sessionstore.max_resumed_crashes
> 
> Setting this to '0' (zero) will present the Session Restore screen after
> your 1st 'forced shutdown' if you so desire. 
> 
> Closing this as WORKSFORME.
You need to log in before you can comment on or make changes to this bug.