Unpredictability with sites such as GitHub

[grahamperrin]

Prior to a save, note the comment beneath the opening post:

Some time after a restoration (probably not the subsequent restoration), note the absence of the comment:

Unfortunately I did not capture the steps in between, but I almost certainly used Tab Mover for the movement between windows.

Can you think of any sane explanation?

Might the staleness occur if a quit occurs too soon after a SessionBuddy save? Or (given my wild array of extensions) might something at quit time cause corruption or loss of saved data?

Environment

$ date ; uname -v
Mon 29 Oct 2018 07:12:26 GMT
FreeBSD 13.0-CURRENT r339737 GENERIC-NODEBUG 
$ pkg query '%o %v %R' waterfox
www/waterfox 56.2.3_2 poudriere
$ 

Generally (not specific to SessionBuddy)

The staleness is very often a problem with sites such as GitHub.

If we can't find a reasonable explanation, then I should probably continue to treat the session storage in Waterfox 56.x as inherently (Firefox 56.0.2) unreliable.

Related

Mozilla bug 1330633 - (ss-reliability) Sessionstore reliability tracking

workaround for staleness (outdated content) when e.g. Firefox is used to view GitHub issues · Issue #672 · sindresorhus/refined-github (2017-08-17) reminds me that for the problems with GitHub, I was clutching at straws long before I discovered Waterfox. There's reference to:

• Mozilla bug 706970 - Tabs restored at startup (app tabs, session restore) should be refreshed from server, not in a "stale" state from cache

– however, later in the issue, with added emphasis:

tl;dr re the conversation that followed http://logs.glob.uno/?c=mozilla%23firefox&s=13+Sep+2017&e=13+Sep+2017#c450899 I no longer suspect a cache-related problem. More likely a bug with, or affecting, session storage.

[Ulf3000]

nahh thats just because i havent put an unloader coder into the addon yet, means when it shuts down it doesnt destroy the menu but generates a new one when enabled so you end up with 2 ,3 ,4 menus ..

leave this open please .. for now i think its alright since it doesnt harm but its obviously not optimised , i was just too lazy at that point to write the unloader, treat it as a kind of script right now then a full fledged extension.. but ill do it eventually

[grahamperrin]

OK, I'll close this issue. Without using SessionBuddy I coincidentally reproduced what seems to be a session storage issue whilst using Discord.

OK I'm going to abandon Discord but it was coincidentally a good opportunity to demonstrate what is, I think, seriously messed up session storage -- the 'Now you see it, now you don't' effect after closing then reopening a tab.