Firefox 82.0.2 (64-bit) destroyed all my OneTab Links and all the Opened Tabs
I am using Firefox 82.0.2 (64-bit) - It is crashed multiple times just after the recent updates a couple of days ago, then destroyed my OneTab today, more than 2600 links stored over two years had gone and all the Opened Tabs. Please help me get back the OneTab Links! Tried to restore the previous version of the Firefox profile but received an error: 0x800704C8
All Replies (6)
Have you tried rebooting the computer?
In the address bar, type about:crashes<enter>.
Note: If any reports do not have BP- in front of
the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.
Please, Do not post a screenshot ! !
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
I think that OneTab has a feature to export its tab lists, Haven't you use this feature to have a backup ?
Are you still using your original profile with this extension installed ?
See also:
I followed your guide: In the address bar, type about:crashes. Note: If any reports do not have BP-in front of the numbers/letters, click it to submit them. Here are the report numbers:
Submitted Crash Reports Report ID Date Submitted bp-05020997-9095-4d66-b04f-1da030201108 11/8/2020, 8:52 PM bp-362bcd5d-9517-4cad-be3f-21c3b0201108 11/8/2020, 8:53 PM bp-de1923f7-8c6e-41ba-a911-eaf480201108 11/8/2020, 8:53 PM bp-ed9237a1-2537-46c2-af8e-19cf70201108 11/8/2020, 8:53 PM bp-45d8259a-0779-4004-874c-38ad50201108 11/8/2020, 8:53 PM bp-8d88a82f-f4dc-45b4-ae84-13ebb0201108 11/8/2020, 8:53 PM bp-5d1e8fb0-4895-4e5f-b389-2a5e00201108 11/8/2020, 8:53 PM bp-13df8f56-28de-499c-a39d-aaba50201108 11/8/2020, 8:54 PM
Q1. Have you tried rebooting the computer? A. Yes with no luck
Q2. OneTab has a feature to export, Haven't you use this feature to have a backup ?
A. No. I used to have OneTab for years and never happened to lose any of my links, never, that is why I never need to have a backup, unless I have a new laptop.
Q3. Are you still using your original profile with this extension installed ? I think so. I have not change anything in the profile, as I have tried to restore the latest version which taken on 31st of Oct. but I received the abobe mentioned error.
Thank you All for your support. I hope you can help me restore my 2500 links of the Onetab asap as it impact my business. I have no clue ever that Firefox updates could have such dam impact!
bp-05020997-9095-4d66-b04f-1da030201108 bp-de1923f7-8c6e-41ba-a911-eaf480201108 bp-ed9237a1-2537-46c2-af8e-19cf70201108
Signature: OOM | small
MOZ_CRASH Reason (Sanitized) : MOZ_CRASH(OOM)
Crash Reason EXCEPTION_BREAKPOINT +++++++++++++++++++++++++++++++++++++ bp-362bcd5d-9517-4cad-be3f-21c3b0201108 Signature: mozilla::layers::TextureReadLock::Deserialize
MOZ_CRASH Reason (Sanitized) : MOZ_RELEASE_ASSERT(section.shmem().IsReadable())
Crash Reason EXCEPTION_BREAKPOINT
This is for Sumo's Related Bugs 1484288 NEW --- Crash in mozilla::layers::TextureReadLock::Deserialize ++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 81.0.1 Build ID 20200930150533 (2020-09-30)
bp-45d8259a-0779-4004-874c-38ad50201108 Signature: OpenDxva11
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster
https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix
https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram
https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding
https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up
https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down
MemTest LAST UPDATED : 12/04/2020
Could you please run a tool from http://memtest.org/
in order to check the integrity of your RAM?
You will need a thumb or disk drive to install it on.
Do you let Windows handle the page file or did you set a fixed size ?
If you use a fixed size for the page file then try the former and let Windows handle the page file.