Neueste Antworten auf Crash on start, just after saved tabs are restored, presumably before or when the tab contents start loadinghttps://support.mozilla.org/de/questions/13652762022-01-24T00:20:30-08:00Well done. Be sure to respond to any requests they make.
2022-01-24T00:20:30-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1477625<p>Well done. Be sure to respond to any requests they make.
</p>Cross-linking issue report; https://bugzilla.mozilla.org/show_bug.cgi?id=1751720
2022-01-24T00:08:15-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477622<p>Cross-linking issue report; <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1751720" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1751720</a>
</p>Please remember to post the link to that report here.
2022-01-23T06:40:45-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1477394<p>Please remember to post the link to that report here.
</p>jscher2000 said
Does Firefox run normally in the absence of extensions that query your tabs?
The s2022-01-23T03:46:43-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477335<em><p>jscher2000 <a href="#answer-1477327" rel="nofollow">said</a></p></em>
<blockquote>
Does Firefox run normally in the absence of extensions that query your tabs?
The sample file in the bug has 8,251 tabs, so perhaps available memory is a factor in where the problem begins -- not a hard limit.
</blockquote>
<p>The presence of addon(s) seems to only affect the tab number threshold of when the crashes happen.
</p><p>My main Firefox session is back up and running again now at about 8600 tabs (with my usual addons loaded), after using my scripts to move a number of domains into html files for later retrieval.
</p><p>I'll see if I can't get an appropriate bugreport written up tomorrow.
</p>Oddstr13 said
The scrounger loads the file without errors btw. Chromium hates me for it tho.
Oddstr2022-01-23T03:20:59-08:00jscher2000https://support.mozilla.org/de/questions/1365276#answer-1477327<em><p>Oddstr13 <a href="#answer-1476953" rel="nofollow">said</a></p></em>
<blockquote>The scrounger loads the file without errors btw. Chromium hates me for it tho.
</blockquote>
<em><p>Oddstr13 <a href="#answer-1477073" rel="nofollow">said</a></p></em>
<blockquote>It looks like the trigger of the crash could be related to loading more than 10k tabs.
</blockquote>
<p>I'm amazed the JavaScript libraries can handle it!
</p>
<blockquote>Removing any combination of windows to bring the tab count below 10k seems to allow the session to load fine (in my testing profile at least).
I'm 99% sure this worked in previous versions, as I know I've been above multiple times before.
</blockquote>
<em><p>Oddstr13 <a href="#answer-1477076" rel="nofollow">said</a></p></em>
<blockquote>The full session file does indeed load in v95.0.1 without crashing.
</blockquote>
<em><p>Oddstr13 <a href="#answer-1477245" rel="nofollow">said</a></p></em>
<blockquote>Triggered by successfully loading a session with about 9600 tabs, and opening tabs until crash:
bp-7fe355e3-51a8-4c1c-84a8-761620220123
Triggered by loading a number of tabs near what crashes, and then enabling the FoxyTab addon:
bp-26bcef79-da01-4f56-929a-f57cd0220123
...
While this issue seems somewhat related, and it looks like I might've tripped it once, what I'm seeing is likely something different; <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1716849" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1716849</a>
</blockquote>
<p>Does Firefox run normally in the absence of extensions that query your tabs?
</p><p>The sample file in the bug has 8,251 tabs, so perhaps available memory is a factor in where the problem begins -- not a hard limit.
</p><p>While that bug was filed against Firefox 89, it's possible Firefox 95.0.2 added a patch that inadvertently affects enormous files.
</p><p>The list of highlights in 95.0.2 is very short: "Addresses frequent crashes experienced by users with C/E/Z-Series "Bobcat" CPUs running on Windows 7, 8, and 8.1." <em>Source:</em> <a href="https://www.mozilla.org/firefox/95.0.2/releasenotes/" rel="nofollow">https://www.mozilla.org/firefox/95.0.2/releasenotes/</a> But there could be other changes. I don't know where to find a complete list, and it probably would be arduous to run a <a href="https://mozilla.github.io/mozregression/" rel="nofollow">Mozregression</a> without knowing more intimate build details.
</p><p>Probably best to file a bug and get advice from the developers on narrowing it down.
</p>Here are the scripts I made to debug and test this issue; https://github.com/oddstr13/FirefoxSession2022-01-23T01:36:45-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477296<p>Here are the scripts I made to debug and test this issue; <a href="https://github.com/oddstr13/FirefoxSessionTools/" rel="nofollow">https://github.com/oddstr13/FirefoxSessionTools/</a>
</p><p>I opted to extract a few domains into lists of links in html files as a temporary workaround, and utilize FoxyTab to clean up some other domains.
</p>The exact number of tabs does not seem to matter too much, but it is somewhere near 10k (on my syste2022-01-22T21:31:34-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477245<p>The exact number of tabs does not seem to matter too much, but it is somewhere near 10k (on my system).
</p><p><br>
Do you have any advice on filing the bug-report?
</p><p>I've managed to upload a few more crash reports, one with a new signature (from loading an addon after a slightly slimmed down session)
</p><p>bp-7220a584-1435-4ffe-83c2-5d7f10220122
bp-f652f9d5-7e2b-45af-9804-1b43c0220121
bp-f83fe60a-7439-4ed5-ae61-4e44b0220121
bp-ae94ba15-6c3a-4479-bb81-ac4850220121
bp-be228ec2-dda3-4ec0-83b0-aa25a0220121
bp-8c80a016-04a4-4305-9313-596030220123
bp-a697d335-caf7-4f79-88fb-3b8930220123
bp-2620a1e2-ead0-4d43-a3bc-5b7f00220123
bp-6f03d541-e620-45a3-a454-f98f00220123
bp-98ae3ce5-4e63-41fc-a174-7362d0220123
bp-3dde16c2-2c9f-433a-b111-03dc40220123
bp-4cea4b27-1b4c-4a5f-a8c2-d39b90220123
bp-36d4ca2c-c871-4708-afb0-bbd1f0220123
bp-5df47f71-1e47-47fd-8c61-705e20220123
bp-c0012a2a-7bdf-486c-9b72-605860220123
bp-e903dd5d-50fd-4c2a-877b-8be5b0220123
</p><p><br>
Triggered by successfully loading a session with about 9600 tabs, and opening tabs until crash:
bp-7fe355e3-51a8-4c1c-84a8-761620220123
</p><p>Triggered by loading a number of tabs near what crashes, and then enabling the FoxyTab addon:
bp-26bcef79-da01-4f56-929a-f57cd0220123
</p><p>The tab distribution over windows in my session file:
Window 1: 7865
Window 2: 148
Window 3: 205
Window 4: 162
Window 5: 842
Window 6: 51
Window 7: 54
Window 8: 41
Window 9: 83
Window 10: 173
Window 11: 11
Window 12: 20
Window 13: 168
Window 14: 69
Window 15: 26
Window 16: 18
Window 17: 26
Window 18: 53
Window 19: 83
Window 20: 77
Window 21: 309
Window 22: 3
Window 23: 3
Total tabs: 10490
</p><p><br>
While this issue seems somewhat related, and it looks like I might've tripped it once, what I'm seeing is likely something different; <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1716849" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=1716849</a>
</p><p>I am able to reproduce `mozilla::dom::Promise::AppendNativeHandler` at-will.
</p><p>`js::UnwindEnvironment` was tripped by loading an addon while near the tab limit, and likely has the same root cause. I haven't been able to reproduce this one, but I haven't made many attempts at it.
</p><p>I'm not sure of what condition produced `mozilla::loader::ImportModule` (but probably bug#1716849).
</p>I think you need to fill out a bug report.
Make sure you include all information they will need to f2022-01-22T06:48:38-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1477107<p>I think you need to fill out a bug report.
Make sure you include all information they will need to fix the issue.
</p><p>Read this first: <a href="https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html" rel="nofollow">Bug Writing Guidelines</a>{web link}
</p><p>Then go to: <a href="https://bugzilla.mozilla.org/" rel="nofollow">https://bugzilla.mozilla.org/</a>
Be sure to include everything that the people there need to know.
</p>I accidentally downgraded only the language pack before.
The full session file does indeed load in v2022-01-22T03:39:06-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477076<p>I accidentally downgraded only the language pack before.
</p><p>The full session file does indeed load in v95.0.1 without crashing.
</p>It looks like the trigger of the crash could be related to loading more than 10k tabs.
Removing any 2022-01-22T03:30:49-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477073<p>It looks like the trigger of the crash could be related to loading more than 10k tabs.
</p><p>Removing any combination of windows to bring the tab count below 10k seems to allow the session to load fine (in my testing profile at least).
</p><p>I'm 99% sure this worked in previous versions, as I know I've been above multiple times before.
</p>This article is helpful for parsing the session file; https://www.foxtonforensics.com/blog/post/anal2022-01-22T03:27:32-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1477072<p>This article is helpful for parsing the session file; <a href="https://www.foxtonforensics.com/blog/post/analysing-firefox-session-restore-data-mozlz4-jsonlz4" rel="nofollow">https://www.foxtonforensics.com/blog/post/analysing-firefox-session-restore-data-mozlz4-jsonlz4</a>
</p><p>In particular, the fact that the jsonlz4 files has the header `b"mozLz40\0"` followed by block mode lz4.
</p>Tell Chromium to get over it.
2022-01-21T21:48:18-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1476991<p>Tell Chromium to get over it.
</p>The scrounger loads the file without errors btw. Chromium hates me for it tho.
2022-01-21T18:20:46-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1476953<p>The scrounger loads the file without errors btw. Chromium hates me for it tho.
</p>Do you have a link to the specifications of the session file?
Details on the compression format, and2022-01-21T17:59:57-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1476951<p>Do you have a link to the specifications of the session file?
</p><p>Details on the compression format, and the structure of the underlying json file?
</p><p>How can I tell if the file is corrupted?
</p>Oddstr13 said
Copying sessionstore.jsonlz4 over to the new profile, and then restoring previous sess2022-01-21T05:26:36-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1476772<em><p>Oddstr13 <a href="#answer-1476648" rel="nofollow">said</a></p></em>
<blockquote>Copying sessionstore.jsonlz4 over to the new profile, and then restoring previous session from the history menu also causes the crash.
</blockquote>
<p>I suspect the file is corrupted. Delete it with Firefox closed.
</p><p><br>
<strong>Don't delete the files</strong> if you need to rescue any data from
them, just move them out of the profile folder to some
location where Firefox doesn't look for them. You can
try to read out their contents using this tool:
<a href="https://www.jeffersonscher.com/res/scrounger.html" rel="nofollow">https://www.jeffersonscher.com/res/scrounger.html</a>
</p>FredMcD said
One option would be to move parts of the original profile into a new one.
Copying sessi2022-01-20T21:19:56-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1476648<p>FredMcD <a href="#answer-1476641" rel="nofollow">said</a></p>
<blockquote>One option would be to move parts of the original profile into a new one.</blockquote>
<p>Copying sessionstore.jsonlz4 over to the new profile, and then restoring previous session from the history menu also causes the crash.
</p><p>Crash reporter is not creating any further files in ~/.mozilla/firefox/Crash Reports/submitted/
but the log file is saying the report was submitted;
[Fri 21 Jan 2022 02:15:44 PM CET] Crash report submitted successfully
</p>Oddstr13 said
Does not happen in new profile.
One option would be to move parts of the original pro2022-01-20T21:03:29-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1476641<em><p>Oddstr13 <a href="#question-1365276" rel="nofollow">said</a></p></em>
<blockquote>Does not happen in new profile.
</blockquote>
<p>One option would be to move parts of the original profile into a new one.
</p>bp-ae94ba15-6c3a-4479-bb81-ac4850220121 = Uptime 29 seconds
bp-be228ec2-dda3-4ec0-83b0-aa25a0220121 2022-01-20T21:02:06-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1476640<p>bp-ae94ba15-6c3a-4479-bb81-ac4850220121 = Uptime 29 seconds
bp-be228ec2-dda3-4ec0-83b0-aa25a0220121 = Uptime 35 seconds
bp-f83fe60a-7439-4ed5-ae61-4e44b0220121 = Uptime 30 seconds
</p><p>Signature: mozilla::dom::Promise::AppendNativeHandler
</p><p>Crash Reason SIGSEGV / SEGV_MAPERR
++++++++++++++++++++++++++++++++++++++++++++++++
bp-f652f9d5-7e2b-45af-9804-1b43c0220121 = Uptime 46 seconds
Signature: mozilla::loader::ImportModule
</p><p>MOZ_CRASH Reason (Sanitized)&nbsp;:
Failed to load critical module "resource://gre/modules/WebNavigation.jsm"
</p><p>Crash Reason SIGSEGV / SEGV_MAPERR
</p><p>This is for Sumo's Related Bugs
1724000 NEW --- Crash in [@ mozilla::loader::ImportModule]
</p>While v95 crashes and seemingly submits the crash log, I am unable to find the corresponding crash i2022-01-20T20:57:42-08:00oddstr13https://support.mozilla.org/de/questions/1365276#answer-1476639<p>While v95 crashes and seemingly submits the crash log, I am unable to find the corresponding crash id.
</p>Product Firefox
Release Channel release
Version 96.0.1
Build ID 20220113185450 (2022-01-13) Buildhub2022-01-20T20:56:04-08:00fredmcd-hotmailhttps://support.mozilla.org/de/questions/1365276#answer-1476638<p>Product Firefox
Release Channel release
Version 96.0.1
Build ID 20220113185450 (2022-01-13) Buildhub data
OS Linux Mint 19.3 Tricia
OS Version 0.0.0 Linux 5.4.0-96-generic #109~18.04.1-Ubuntu SMP Thu Jan 13 15:06:26 UTC 2022 x86_64
</p><p><br>
https://support&#46;mozilla&#46;org/en-US/kb/update-firefox-latest-version?cache=no
Did you update Firefox to the latest version?
</p><p>Version 96.0, first offered to Release channel users on January 11, 2022
Version 96.0.1, first offered to Release channel users on January 14, 2022
</p><p><br>
<a href="https://support.mozilla.org/en-US/questions/1359657#answer-1463359" rel="nofollow">https://support.mozilla.org/en-US/questions/1359657#answer-1463359</a>
and updated to 95.0. . . . I finally found where the plugin "Widevine Content Decryption
Module provided by Google Inc." was not updating to the newest version of
December 1, 2021. Ver #4.10.2391.0
</p><p>cor-el;
Make sure you have the latest Widevine version. You can toggle DRM off/on to
see if that makes Firefox (re)load DRM components.
</p>
<ul><li> Settings -&gt; General: Play DRM
</li><li> <a href="https://support.mozilla.org/en-US/kb/enable-drm" rel="nofollow">https://support.mozilla.org/en-US/kb/enable-drm</a>
</li></ul>
<p>You can possibly check the XHR requests in the Browser Console if this doesn't work.
</p>
<ul><li> <a href="https://developer.mozilla.org/en-US/docs/Tools/Browser_Console" rel="nofollow">https://developer.mozilla.org/en-US/docs/Tools/Browser_Console</a>
</li></ul>