975861 - Restoring all tabs does not work

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[JD]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24 (Beta/Release)
Build ID: 20140203230027

Steps to reproduce:

One of my current seetings is:
Edit->Preferences->Browser
      Display on "Browser Startup"
           "Restore Previous Session"
      "Restore All Tabs Immediately"

However, when I exit the browser and restart it,
none of the tabs are restored and I just get one blank tab.




Actual results:

One empty tab displayed


Expected results:

All my tabs should have been restored.

Comment 1

[Tony Mechelynck [:tonymec]]

IMHO, this is the kind of thing which ought to be built-in (and working) in the browser; however, as long as it isn't (and maybe even when it'll be), I recommend the Session Manager extension, https://addons.mozilla.org/addon/session-manager/

This way, even if (because of a crash, let's say, or even -accidents happen- because the cleaning lady pulled the plug by mistake) your last session is only partly saved, you'll be able to restore a somewhat earlier version, hopefully not _too_ different.

Note: With my 100 or so tabs, I found "Restore all tabs immediately" to be a little too hungry of bandwidth (and therefore slow). With "Restore only [___] tabs at a time", the default is 3, but upping it to 5 still doesn't seem too heavy AFAICT. The tabs start reloading at once, starting with the one you're looking at, but the other ones "queue up at the booth", so to speak: you can see the throbbers chase each other along your tab bar until all tabs have been reloaded.

Of course, if you open each page in a separate movable frame, they are windows, not tabs, and if you close them one by one, they stop being part of your session: at restart, SeaMonkey will only reload what was still present when you used Ctrl+Q or File→Quit (I'm on Linux; on Windows it could be Ctrl+X and File→Exit instead, and on the Mac Cmd+Q and SeaMonkey→Quit — or something more or less like that).

Comment 2

[andré]

I have exactly the same problem with 2.25 final release.
It probably started with 2.24 or earlier.  (I only install final releases.)

My settings are the same except I restore only one tab at a time, to avoid freezes while it loads my 50-100 tabs.  (As Tony suggests in comment 1.)
(I don't care if it takes 5 minutes to load them all.  It prioritizes the current tab.)
I'm on 64-bit Linux, using the 32 bit version of Seamonkey (to get proper localization).

I've been using bookmark / "save group of tabs" before closing to allow recovering my tabs, although I often forget.
If I don't close Seamonkey before rebooting or logging out of my session, then Seamonkey usually (but not always) offers to restore all my tabs.

I'm going to try the session manager extension recommended in comment 1.  It is a real pain trying to recover all the tabs when I loose them.

Comment 3

[therube]

As a test, create a new, clean Profile & see if your tabs restore correctly there.

If that works, then see if restarting in Safe Mode works in your old Profile.
(Help | Restart with Addons Disabled)

(Note the SeaMonkey 2.26.1 is the current release.)

Comment 4

[Tony Mechelynck [:tonymec]]

In reply to comment #2:
Actually, I recommend loading them 5 at a time (if not "all at once" the default is 3). In my experience (and on my machine) this seems to be a good compromise between loading all tabs at a reasonably fast pace, and still leaving some bandwidth for non-Browser activities such as Mail, News and IRC chat.

With my 108 startup tabs, this still takes some time, but that's OK by me. The current tab is indeed loaded first, and for the rest I can see the little throbbers play leapfrog around the tab bar; also, my [profile]/chrome/userChrome.css http://users.skynet.be/antoine.mechelynck/other/userChrome-seamonkey.css has some rules to give tabs a different background colour once they are loaded, so I can see how far the jumping throbbers are to the finish line.

Comment 5

[Tony Mechelynck [:tonymec]]

With two users complaining about the same symptoms, plus me having taken explicit steps to work around them, I think this bug deserves Confirming.

Comment 6

[JD]

(In reply to Tony Mechelynck [:tonymec] from comment #5)
> With two users complaining about the same symptoms, plus me having taken
> explicit steps to work around them, I think this bug deserves Confirming.

I would not argue with that.

Comment 7

[andré]

Fixed by changes in sm 2.30
Both 32-bit official release + 64-bit iceape (rebranded by Linux distributions)
Works very nicely now :)
(It still didn't work in sm 2.29)

Could someone with privileges please close as "resolved / fixed" ?

Comment 8

[JD]

(In reply to andré from comment #7)
> Fixed by changes in sm 2.30
> Both 32-bit official release + 64-bit iceape (rebranded by Linux
> distributions)
> Works very nicely now :)
> (It still didn't work in sm 2.29)
> 
> Could someone with privileges please close as "resolved / fixed" ?

I just tried it.

IT WORKS.

Now, if only it would restore my
SM windows to the same workspace they were in when
I logged out (i.e. when I login and start SM, all it's windows
should be opened into the same workspaces they were in when 
I logged out).

Even FF is unable to do this!!

Comment 9

[andré]

Unfortunately, sessionrestore only worked once for me.
Now, unlike the previous versions where the last tabs were listed but the restore button was greyed out, the last tabs are not even listed.
The trick of renaming sessionrestore.bak to sessionrestore.json doesn't work.
Strangely, if I add a few tabs to a new session, they are restored.  But not the almost 100 of my useful tabs.  (Which vary considerably over time, so a static multi-tab bookmark is not very useful.)

Maybe there is something in my "useful" tabs that mozilla doesn't like ?

Comment 10

[andré]

ok, really strange.  I retried it, and this time it worked 100%.
But I noticed that sessionstore.json is really small compared to previous versions (69k vs 400k), meaning either the tab info is stored elsewhere or there was a lot of useless info inside before.
(When I got a blank page it was only 155 bytes.)
Maybe the problem is leaving sm running for a long time ?  (Sometimes several days.)

It didn't ask me to restore as it used to, just went ahead, which is exactly what I want.
So it looks like it is indeed fixed.

Comment 11

[Tony Mechelynck [:tonymec]]

Resolving WFM according to reporter's comment #10.