1435563 - Session not remembered correctly. Some tabs are *missing* after restart

Status: RESOLVED WORKSFORME

(Firefox :: Session Restore, defect)

Description

[jabol240]

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

Steps to reproduce:

Using latest firefox on Arch Linux. I have over 1000 tabs open (obviously I don't load them all on startup). 12 GB RAM. For at least a few months browsing session is not remembered correctly. Steps to reproduce: just close firefox.


Actual results:

After starting again, some tabs are missing (I had *20* tabs missing on one occasion). This happens regularly, probably every time. Only tabs opened in this last session (new tabs) seem to be affected, i.e. tabs from previous sessions seem to be remembered reliably. Also, sometimes - but rarely - tabs are replaced with empty tabs (new tabs). Also, sometimes the URLs are replaced with the URL of the previous site before redirection (or generally a URL from this tab's history, I am not sure).


Expected results:

Browsing session should be restored correctly, by all means.

Comment 1

[jabol240]

Tabs visited shortly (seconds, minutes) before closing firefox tend to be inexistent after restart. Also tabs that had been opened in background and never visited. But these don't seem to be only culprits. Also I admit that my RAM tends to be around 90% used (i.e. around 1 GB RAM is still available typically) when I restart firefox (as shown by htop app).

While I have attention... why the sessionstore & other session files are so big and who needs that? My session files are around 10 MB each. While all I need is a list of URLs in open tabs, which is a ~100 KiB file. Okay, add a 10-deep history for each tab. Who needs more??? Not only it wears out SSDs and uses resources but is also seemingly unreliable...

Comment 2

[Mike de Boer [:mikedeboer]]

Hi jabol, apology for the late reaction.

I'm afraid I can't reproduce this with the STR you provided... There have been quite a number of reliability improvements in the meantime, so I'm also wondering whether this is still an issue for you in Firefox 60?

In the meantime I'll close this bug, but feel free to reopen when you are able to provide reliable STR.