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

Firefox crashes after the session has been running for a couple of minutes

  • 5 replies
  • 1 has this problem
  • 506 views
  • Last reply by lcarver

more options

It seems like when I have the Tools .. Options dialog active, that makes the entire session crash. I have not gone through all the steps to determine whether the crash will stop if I disable an extension. But I thought that Classic Theme Restorer should be harmless. Likewise with my selected theme, I will try disabling one or both of those. LastCrash is 1455739927

Crash ID: bp-3b5f1371-860d-476f-960d-d4f182160217 Crash ID: bp-fdaa2980-c244-48f0-886e-fa1d42160217

[02/17/16 11:30:43] Crash report submitted successfully [02/17/16 12:12:47] Crash report submitted successfully

Chosen solution

Thanks a lot, cor-el. I understand my FF sessions were crashing due to memory allocation failures. (I wish that FF had preallocated enough resources to inform me of that, at the time;) I have now cleaned up my problem.

It so happens I had not restarted my computer since September 2015. (Coincidentally, software updates were stuck since then as well; I've managed to fix it all.) And my (Intel) graphics drivers were current. I'll continue using hardware acceleration at this time. Now that I finally know what to look for, in case my system should have severe memory fragmentation in the future, I'll be able to recognize it. Thanks again ... Larry

Read this answer in context 👍 0

All Replies (5)

more options

My crashing issue has begun after yesterday, when I decided to move to a new, refresh FF profile as part of beginning some housecleaning on my profile. After migrating to the new profile, I installed a couple of extensions including a theme, AdBlockPlus, and Classic Theme Restorer. And one that added a Restart button in the Customized pane. Now, I have tried disabling my chosen theme, which is called FT DeepDark. Afterward, I was once again in Tools .. Options .. Applications trying to get FF to send PDF content to the in-browser Foxit PDF plugin handler, instead of having it send all PDFs to an external application. By clicking on those content type handler option/choice combo fields, it made FF crash once again. Crash Reporter raised a message window, stating the following: The application had a problem and crashed. Unfortunately, the crash reporter is unable to submit a report for this crash. Details: The application did not identify itself.

[~...crashes/events]$ cat e21ae68a-f1cf-4c40-8437-6c64b9fea71b crash.main.2 1455743214 e21ae68a-f1cf-4c40-8437-6c64b9fea71b SecondsSinceLastCrash=3287 BlockedDllList= SystemMemoryUsePercentage=63 TotalVirtualMemory=4294836224 AvailableVirtualMemory=381767680 TotalPageFile=22894608384 AvailablePageFile=9687572480 TotalPhysicalMemory=16861937664 AvailablePhysicalMemory=6118805504 MozCrashReason=MOZ_CRASH() OOMAllocationSize=1

more options

LastCrash is 1455743214 Crash ID: bp-3b5f1371-860d-476f-960d-d4f182160217

I've now (after the crash just mentioned above) disabled the Classic Theme Restorer extension, and disabled the Restart extension, and then restarted FF with session restoral, i.e. session restored. Then I went back and started toggling settings in About .. Config .. Applications, like before. After several minutes now, there is no crash.

I'll begin to re-enable my extensions and will see if the crash comes back, or not. At some point, if it crashes again I will have to put some or all CTR (Classic Theme Restorer) settings all back to their defaults, if problems recur. If they don't, I will probably re-enable my chosen theme FT DeepDark last.

more options

FF crashed again, with CTR enabled. I was back in those content handler options settings, clicking on choices for each MIME type. I have not enabled an alternate theme, i.e. am using Default (theme); so the current issue is not related to FT DeepDark. I forgot to mention I had installed the Search Tab extension (as well as QuickNote and Places Maintenance) ... will disable those three extensions, and will disable AdBlockPlus and Panorama (Tab Groups), now.

[~...Firefox/Crash Reports]$ cat crashes/events/6cce04ab-4c80-47bd-9f43-5d65e8498c54 crash.main.2 1455746296 6cce04ab-4c80-47bd-9f43-5d65e8498c54 SecondsSinceLastCrash=3082 BlockedDllList= SystemMemoryUsePercentage=64 TotalVirtualMemory=4294836224 AvailableVirtualMemory=268713984 TotalPageFile=22894608384 AvailablePageFile=9701179392 TotalPhysicalMemory=16861937664 AvailablePhysicalMemory=5940875264 MozCrashReason=MOZ_CRASH() OOMAllocationSize=1

more options

The crashes are out-of-memory crashes where Firefox fails to allocate required memory.

  • OOM Allocation Size :1112

The System Memory Use Percentage isn't that high, so it is possible that the memory is fragmented.

You can try to disable hardware acceleration in Firefox.

  • Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"

You need to close and restart Firefox after toggling this setting.

You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.

Start Firefox in Safe Mode to check if one of the extensions (3-bar Menu button/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: 3-bar Menu button/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
more options

Chosen Solution

Thanks a lot, cor-el. I understand my FF sessions were crashing due to memory allocation failures. (I wish that FF had preallocated enough resources to inform me of that, at the time;) I have now cleaned up my problem.

It so happens I had not restarted my computer since September 2015. (Coincidentally, software updates were stuck since then as well; I've managed to fix it all.) And my (Intel) graphics drivers were current. I'll continue using hardware acceleration at this time. Now that I finally know what to look for, in case my system should have severe memory fragmentation in the future, I'll be able to recognize it. Thanks again ... Larry