674816 - Session Restore in 2.4a series does not restore all tabs

Status: RESOLVED WORKSFORME

(SeaMonkey :: Session Restore, defect)

Description

[Kelly Clowers]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0a2) Gecko/20110725 Firefox/7.0a2 SeaMonkey/2.4a2
Build ID: 20110725013002

Steps to reproduce:

I restart SeaMonkey to upgrade to a newer nightly build (auto-downloaded).


Actual results:

With several windows open, each with several tabs, the original window (never the later windows) does not have all its tabs restored when SeaMonkey comes up from a clean shutdown.

I have 20-30 tabs in the first window (~8 are restored, always the same ones - and which ones and their order suggest it is from a previous session, not actual remnants of the most recent one), 30-40 tabs in the second window, and 4-20 tabs in the third window.



Expected results:

All tabs should be restored.  In previous nightly branches, this problem did not occur even with many more tabs.

Comment 1

[therube]

Can you attach your sessionstore.json file?
(Note it may contain data not wanted for general viewing?)

Comment 2

[Kelly Clowers]

Attachment: session restore data

Comment 3

[Kelly Clowers]

Should be fine to have my session restore data on here...

It is probably important, though, that while this happened every time I restarted for several days (3-4 restarts), I restarted once more between the report and now, and this time all tabs were preserved.

Comment 4

[therube]

(Right-click on a Tab, Close Other Tabs, gives you a count of the other tabs.)
(Setting  browser.sessionstore.max_concurrent_tabs;0  makes it much quicker to restart & not all the content loads, less "noise" ;-) )

Quitting & Restarting, I repeatedly get ~15, ~35, ~3, tabs per window.

Could it be that it only happens after a .mar update ?

Comment 5

[Kelly Clowers]

Just did a .mar update, everything worked fine. I am wondering if this was caused by a system update that I did not reboot after. Although it seems like Mozilla is mostly self-contained (static linking?). I have had really weird results in cases where I did not restart (at least X) after gtk/glib updates or libc updates, and I did reboot right before it started working right.

Comment 6

[Philip Chee]

Sounds like Bug 673902 which will be fixed in SeaMonkey 2.5.

Comment 7

[Phoenix]

Is this still reproducible after SeaMonkey 2.5 released?

Comment 8

[Phoenix]

Resolved per whiteboard