1180371 - Starts (intermittently) with about:sessionrestore if not quit from the menu

Status: RESOLVED WORKSFORME

(Firefox :: Session Restore, defect)

Description

[Aloysius]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 2015063000

Steps to reproduce:

Closed Firefox window from the gadget.


Actual results:

Launched Firefox and about:sessionrestore was open.


Expected results:

Tabs should have been restored without asking.

Comment 2

[Noah (NoahSUMO/SolidSnake) [:Noah]]

Reopening bug. You were right to file a new bug. Developers don't like reopening old bugs after years have passed. 2013 in this case.

We need someone else to confirm they see this too. Then we need to find the steps to reproduce this so the developers can reproduce it as well. They might need your sessionstore.js file for that. But if there's any personal info in it, you don't have to upload it here. A developer might ask you to email it to them instead.

But bug 845681 seems to be what you're seeing but not consistently. How many windows do you have open? Are any of them private windows?

Comment 3

[Aloysius]

(In reply to Noah (oldtimer) [:Noah] from comment #2)
> But bug 845681 seems to be what you're seeing but not consistently. How many
> windows do you have open? Are any of them private windows?

On second thought, given the inconsistent nature of the problem, I'm not even sure not using File/Quit is even a factor.

> How many windows do you have open? Are any of them private windows?

From 15-20 to 4-5 or 1. I'm not sure it does it with zero.
It also happened with a fresh profile...

Should I save sessionrestore.js the next time it happens?

Comment 4

[Cesar Eduardo Barros]

Several Fedora users are seeing this. See the following URLs:

https://bugzilla.redhat.com/show_bug.cgi?id=1239231
https://admin.fedoraproject.org/updates/FEDORA-2015-11084/firefox-39.0-6.fc22
https://admin.fedoraproject.org/updates/FEDORA-2015-11126/firefox-39.0-6.fc21

For me in this computer, it's happening every time (I only tested closing the window, however; didn't try File > Quit yet).

Comment 5

[Cesar Eduardo Barros]

Attachment: sessionstore.js

The sessionstore.js file from one of my attempts. Copied after closing Firefox and before starting it again; it seems to erase this file when starting.

I set all cookies to clear on exit, only opened this page and the other three I mentioned, and I manually reviewed the file, so it shouldn't have any private information.

Comment 6

[gbcox]

(In reply to Cesar Eduardo Barros from comment #4)
ject.org/updates/FEDORA-2015-11126/firefox-39.0-6.fc21
> 
> For me in this computer, it's happening every time (I only tested closing
> the window, however; didn't try File > Quit yet).

I tried File > Quit and am having the same issue.  Happens every single time I close Firefox and restart.

Comment 7

[Aloysius]

Attachment: sessionstore.js

Now the problem is at pretty much every start. I added my sessionstore.js as attachment.

Comment 8

[:Gijs (he/him)]

For people who are seeing this - what shows up if you load 'about:crashes' ? Is there basically a crash for every time you close the browser? Can you copy the links to those crash reports into this bug, please? :-)

Comment 9

[Aloysius]

(In reply to :Gijs Kruitbosch from comment #8)
> For people who are seeing this - what shows up if you load 'about:crashes' ?
> Is there basically a crash for every time you close the browser? Can you
> copy the links to those crash reports into this bug, please? :-)

I haven't seen this in a few releases.

Comment 10

[:Gijs (he/him)]

(In reply to Aloysius from comment #9)
> (In reply to :Gijs Kruitbosch from comment #8)
> > For people who are seeing this - what shows up if you load 'about:crashes' ?
> > Is there basically a crash for every time you close the browser? Can you
> > copy the links to those crash reports into this bug, please? :-)
> 
> I haven't seen this in a few releases.

OK. Then I'll close this as 'works for me' for now, and if people are still seeing this, they can either reopen this report or file a new one, whilst providing more (and more up-to-date) details. Thanks!