Not much hope I'm afraid
1.8 was a special build and I don't know if it was still using the same session system as 1.7, but probably.
In the official builds the session system was changed in KM75 (or 74?) and since then stores the addresses in a separate file. Look inside your current profile folder if there's some file named "session..."?
If not, the
OLD sessions plugin worked like this:
- during a session, current adresses were stored inside
prefs.js in the profile folder, as "last session". Each page address is only saved after the page is fully loaded.
- if the browser gets closed normally, KM overwrites (before shutting down) the old "Previous Session" with the current "Last Session"
- at each browser start, the old "Last" session gets deleted again and a new one gets started
- if the browser crashed, the stored "Previous Session" is not updated and still the "next-to-last" session!
==> KM can only restore the last regularly-closed "previous session".
BEFORE restarting the browser after a crash, the crashed session is still stored as "Last Session" in prefs.js - but will get
deleted again as soon as the browser is restarted. So the first rescue action is to make a backup copy of that file, then try to fix it with a macro or manually.
If not, your only chance is probably to recover those few tabs that had already fully loaded in the first restoring attempt before all froze up. Before starting that browser again, I'd make a
copy of prefs.js in current profile folder and look inside it with a text program, what may be left...or not...
=====
That said... but perhaps your HISTORY still holds the adresses??
Stored in profile folder too, old system history.dat, new one guess places.sql
Edited 2 time(s). Last edit at 05/25/2015 10:53AM by siria.