This one above my paygade, I will need to let someone else give you proper advice, or wait until Fx45 has been out longer and other similar reports surface. The crashes are apparently memory related despite you still having available memory. I also notice graphical critical errors are mentioned.

My suggestions for now are

1. Try in safemode an with all plugins disabled.
   • Diagnose Firefox issues using Troubleshoot Mode
     Disable or remove Add-ons
     If that does not help:
2. Do a clean install of Fx45 involving deletion of the program files. (Please TAKE CARE not to delete the profile)
   • Firefox keeps crashing at startup_try-a-clean-install Does that help ?
3. If not: Try temporarily installing and using Firefox ESR instead of Fx45
   1. As a precaution backup your current profile first see Back up and restore information in Firefox profiles
   2. https://www.mozilla.org/firefox/organizations/ That should install over the top of Fx45.

Use of ESR is not normally recommended, or supported by Mozilla for use by individuals, but it will be a more secure option than trying to downgrade, and if Fx45 crashes every few 10s of minutes it is not useable for work. I have a suspicion this may turn out to be a regression in Firefox 45 .

Forum notes

• Reports for Your Crash IDs
  1. bp-0bb7091a-00fe-49ec-81cb-f88c72160316
     bp-876dab18-bbd7-4235-8720-16ebb2160316
  2. bp-7be43b55-106c-4099-96bc-abf942160316
  3. bp-d1e9ce10-be1b-4ab1-80f1-a3fd72160316
• Crash Signatures
  • Signature: OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xrealloc | nsTArray_base<T>::EnsureCapacity<T> | nsTArray_Impl<T>::AppendElement<T> | mozilla::a11y::EventQueue::PushEvent
  • Signature: OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xrealloc | nsTArray_base<T>::EnsureCapacity<T> | nsTArray_Impl<T>::AppendElement<T> | mozilla::a11y::EventQueue::PushEvent
  • nsAccessibilityService::MarkupRole
• Potentially related bugs
  • Bug 1240137 ...
  • Bug 1218446 - crash in nsAccessibilityService::MarkupRole
• Metadata includes GraphicsCriticalError |[0][GFX1-]: [D2D1.1] 4CreateBitmap failure Size(28,30647) Code: 0x80070057 format 0|[1][GFX1-]: [D2D1.1] 4CreateBitmap failure Size(28,30647) Code: 0x80070057 format 0

Alright thanks for replying.

I'll try using safe mode tomorrow for work and reply if I still get any crashes.

I was also considering downgrading to an older version but will check out if this ESR thing can help.

Safe mode may help for instance that disables hardware acceleration. Old versions should be avoided, it would be safer to use an alternative browser that is up to date.

If you try ESR note it is still available for a transitional period as a Fx38 based version. That has critical security fixes back ported to it, so it is safe to use but probably will not have the problem with crashes. (English US Windows Fx version 38.7 link)

bp-c10ecd57-86cf-4a6b-a026-bfa4a2160317 bp-2609e376-2c70-493b-ae29-6a5222160317

Happened 4 times today even in safe mode and i also tried refreshing its settings but it still crashed. (Only 2 above reports were submitted though).

Only thing left is to try the ESR version. I am going to install ESR 45.

Why is this happening?

Its probably better to try Fx38.7 ESR rather than FX45 ESR. It is even better to try the special clean install steps with the standard Firefox Release first.

Having looked further into your crash reports I note that the Crash Signature is very rare. You may even account for all those Windows 10 signatures (ca 60/week). Putting this into perspective another current issue I looked at is generating ca 10,000/week. That almost certainly rules out my suspicion of it being a Firefox regression issue.

Trying ESR may well help, but in fact my advice would be for you to first of all try a clean reinstall of the standard Firefox 45. That will be Fx45.0.0 , and any day now will update to Fx45.0.1

Note that was my initial advice in step 2 of #answer-856538, but I am not sure you got that far and tried the special clean install procedure I suggested.

Before posting the problem i already did a clean re-install.

I did it again just now. Attached is a screenshot of program files folder.

I also removed mozilla folders from "users>appdata" (local).

Lets see if it crashes again.

Thanks for the confirmation.

OOPs !!

Removing other folders is not a good idea. If you remove Firefox profile folders you will lose bookmarks and passwords etc.

• Profiles - Where Firefox stores your bookmarks, passwords and other user data

Ordinarily that folder should only be temporarily renamed, or changed by use of Firefox Refresh|(was Reset) (Which creates a backup before changing it)

• Refresh Firefox - reset add-ons and settings

You should try to get back what you can by using Windows feature for recovery of Previous Versions of Files & Folders (I think Windows keeps versions by default, but not sure how often.)

• http://windows.microsoft.com/en-gb/windows/previous-versions-files-faq#1TC=windows-7 (I could not see a Windows 10 version of that advice )

I took a backup and I have my bookmarks etc synced with Mozilla account. So no worries there. But my problem still stands.

hi, could you please try the following: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named accessibility.force_disabled. double-click it and change its value to 1.

philipp said

hi, could you please try the following: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named accessibility.force_disabled. double-click it and change its value to 1.

Done. Now?

please see if the crashes continue :-) if yes, it would be useful if you could attach another new crash id, thanks...

Okay so i have good news. Firefox did not crash this time for atleast half a day now.

I left my system locked for almost 1 hour. Came back and it was still running without any issue.

Don't know what "accessibility.force_disabled" this did exactly but whatever it was i'm happy that it is no longer causing a crash.

Thanks a bunch guys.

It will be worth making a note of the change. The underlying problem may go away and the default setting may again make sense at some time in the future.

You could for instance find the changed setting (despite its name) may prevent proper use of a touch screen. Now as long as you have no touch screen device you will never notice the difference.

That's just it. My laptop has touch screen. And I use it from time to time but it has not caused any trouble since I disabled "accessibility.force".