Announce and Discuss the Latest Theme and Extension Releases.
I am not quite sure whether this is the right place for a feature request:
Is it possible to save a Session containing one or more Windows or Tabs from different Windows from the Crash Recovery Sessionmanager Window. ?
Background: Sometimes, after a crash it is necessary to NOT open all Tabs / Windows from the former Session. But when the Tabs should be kept, it would be useful to save them from the Recovery Window by selecting a window (Tab) or several. Then deactivate them from reopening and look for them later.
Or is there already an option to do this, I haven't found yet?
Edit: I disabled the Work Offline extension from http://multi.nadenade.com/leafy/Mozilla/Offline/ extension. Session Manager seems to be working properly now.
Session Manager doesn't restore both windows of my auto-saved session after the update to Fx 52.0. The second window is blank and a popup is displayed with
followed by what looks like a back trace of the call stack. After rolling back to Fx 51.0.1 the session restores correctly.
The session was created during Fx 51.0.1. "Show my windows and tabs from last time" has been selected for startup.
When Fx 52.0 was started, a popup said that my previous session had crashed. I've been getting that error popup for years everytime Fx is updated. As usual, I selected my named autosaved session to be restored. But this time only one window is properly restored, as I've described above.
I'm working around this issue by sticking with Fx 51.0.1, starting with the profile backup I routinely do before each Firefox update.
The full error message is
Hope this helps.
I get an error pop-up window from SessionManager 0.8.1.13 that a session file is corrupted, but the error message does NOT show the name of the file. Can you please add the full /path/to/file to such error messages?
Actually, it would be great if also the main SM loading interface windows showed the underlying names of the files that are presented, in a separate (maybe optional) column, rather than just the internal name=something field from inside the file.
Same goes for file date, as opposed to the internally saved date in name= or in timestamp=.
The session/window data is corrupted:
JSON.parse: expected ',' or '}' after property value in object at line 1 column 131135 of the JSON data(SyntaxError)
"There was an error decrypting your session/window data. Most likely the session/window data is corrupted".
The session file in question was NOT encrypted. The json portion of the file had been pretty-printed, some fields had been removed, and in the header I had changed the name=[ blah ] line. The json portion of the file passed a jsonlint syntax checker.
Question: What exactly causes SM to think that a file is or is not "encrypted"? Is there an embedded comment, a magic cookie or anything like that which the pretty-printer may have discarded? Does SM require that the json portion of a session file is "packed" or "Dumped" or "serialized", as opposed to "pretty-printed"?
Is the setting to encrypt sessions enabled? A file is considered encrypted if the file does not contain any colons (:) since json always contains colons.
Who is online
Users browsing this forum: No registered users and 1 guest