889796 - browser believes it crashed when it hasn't

Status: RESOLVED DUPLICATE of bug 918276

(Firefox :: Session Restore, defect)

Description

[denizen]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212

Steps to reproduce:

This is the second time I have to report this bug,  and there has been an UPDATE since the first time.  why didn't you guys take my bug report into account?  
I for one,  experience it every single day.

I just used the browser in an everyday way,  opening and closing web pages in multiple tabs.  
the variable browser.tabs.closewindowwithlasttab is set to FALSE.
I want the browser window to stay open when I close the last tab using ctrl-W.




Actual results:

Sometimes the browser is CLOSED with alt-f4 (or even the X at the corner of the window),  and then it thinks it has crashed and opens up the crash recovery screen upon the next restart.  
Also sometimes it flat-out RESTORES the previous session,  even though the last tab was CLOSED manually,  or the window was closed manually.   Sometimes it restores an about:blank page,  also saying it has crashed when it has not.  Closing an about:blank window is not a crash.
None of this happened when browser.tabs.closewindowwithlasttab  was set to true.



Expected results:

The browser never crashed.  it was closed.  There should not be a session restore dialog,  or a session restore altogether.

Comment 1

[Loic]

(In reply to denizen from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 5.1; rv:22.0) Gecko/20100101
> Firefox/22.0 (Beta/Release)
> Build ID: 20130618035212
> 
> Steps to reproduce:
> 
> This is the second time I have to report this bug,  and there has been an
> UPDATE since the first time.  why didn't you guys take my bug report into
> account?  
> I for one,  experience it every single day.

Provide the bug number, please.

And your bug is likely bug 495123.

Comment 2

[denizen]

I don't think 495123 is the same bug.
In my case the session sometimes restores itself with several non-blank tabs.
and somtetimes it restores a blank page.
and sometimes it shows a restore tab list with checkboxes.
I never had any such issues before I changed browser.tabs.closewindowwithlasttab

Comment 3

[[:Aleksej]]

What is your previous report's number (it's not on your current e-mail address)?  Please don't file multiple bugs for the same problem.

There was bug 845681 before Firefox 22.

Comment 4

[denizen]

why don't you guys just try it? 
set the darn variable to true and experience it first hand!

Comment 5

[denizen]

Just updated Firefox to the latest version.
STILL NOT FIXED

the browser restores the previous session even though all tabs had been previously closed using ctrl-W

Comment 6

[(mostly gone) XtC4UaLL [:xtc4uall]]

I can't repro nor have seen that Issue using several Firefox versions (Release/Aurora/Nightly) in the past months.

Can you provide/attach a copy of the "sessionstore.js" file off your profile's dir showing the Issue?
Be sure that public/no privacy related Sites get saved.

Comment 7

[denizen]

Thank you for your response.  
Before I provide this file,  please try this:

1. set browser.tabs.closewindowwithlasttab to FALSE.
2. open 4 different websites (any) in 4 different tabs
3. close all 4 tabs in sequence,  pressing ctrl-w 4 times
4. at this point you should be left with a window showing a blank tab
5. close firefox using the 'X' at the top corner of the window
6. re-open firefox
7. the last session should restore,  even though all tabs were closed manually

you may have to repeat,  sometimes it works sometimes it doesn't

Comment 8

[[:Aleksej]]

Reproduced on the second attempt with 2013-09-16-03-02-01-mozilla-central-firefox-26.0a1.en-US.linux-x86_64

There was 1 blank tab and 4 non-blank tabs opened by middle-clicking in the newtab's grid; I selected the blank tab and pressed Ctrl+W 4 or 5 times, then pressed the [X].

Terminal showed (among warnings related to GLib, GnomeUI and gtk, probably all unrelated) while or after closing of tabs/Firefox:

###!!! [Child][AsyncChannel] Error: Channel closing: too late to send/recv, messages will be lost

Comment 9

[Loic]

It's bug 495123, check the replies.

Comment 10

[denizen]

Is 495123 solved?

Comment 11

[Loic]

No.

Comment 12

[Tim Taubert [:ttaubert] (inactive)]

Duping to bug 918276 based on the STR provided in comment #7 and the verification from comment #8 that mentions it was reproducible on the second try.