We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Denc nañu waxtaan wii. Yónneel yeneen laaj soo soxlaa ndimbal.

Repair damaged recovery.js file?

  • 3 tontu
  • 1 am na jafe-jafe bii
  • 5 views
  • i mujjee tontu mooy carava23

carava23
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.

All Replies (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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.

carava23
carava23 Ki laajte
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?

carava23
carava23 Ki laajte
more options

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