Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Repair damaged recovery.js file?

  • 3 wotmołwy
  • 1 ma tutón problem
  • 5 napohladow
  • Poslednja wotmołwa wot carava23

more options

Hi, so upon restart recently my tabs from the last session weren't recovered. I have two files which contain the links: a recovery.js and a recovery.bak, both of which are very large. I'm familiar with the process of renaming them to sessionstore.js to recover the tabs, but that isn't working for either in this case.

I feel as though there must be some way to edit the files in a reader to force them to be recognized and generated when renamed. Is this possible? There are far too many for me to copy and paste from a reader.

Thanks.

Hi, so upon restart recently my tabs from the last session weren't recovered. I have two files which contain the links: a recovery.js and a recovery.bak, both of which are very large. I'm familiar with the process of renaming them to sessionstore.js to recover the tabs, but that isn't working for either in this case. I feel as though there must be some way to edit the files in a reader to force them to be recognized and generated when renamed. Is this possible? There are far too many for me to copy and paste from a reader. Thanks.

Wšě wotmołwy (3)

more options

Do you know in what way the files are corrupted?

The files will only work if it is possible to parse the content. You can test this by renaming the file and change the file extension to .json Then you can enable the built-in JSON viewer by setting devtools.jsonview.enabled to true on the about:config page and open the file in a Firefox tab.

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

more options

cor-el said

Do you know in what way the files are corrupted? The files will only work if it is possible to parse the content. You can test this by renaming the file and change the file extension to .json Then you can enable the built-in JSON viewer by setting devtools.jsonview.enabled to true on the about:config page and open the file in a Firefox tab. You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

Thanks for your reply.

I don't know what's wrong with the files, only that they won't restore the tabs as normally happens when renamed to sessionstore.js and placed in the relevant folder.

Changing to the .json extension didn't allow the file to be openable in a web browser. It does open in Firefox with .js attached but it's a huge mass of text. Nonethless, the information is there and it seems to me that there should, therefore, be a way to make it work?

more options

If anyone else has a solution, it would be greatly appreciated.