Go to about:crashes and paste here your recent crash IDs.

do you mean just these?

137e41b8-8846-4e23-b120-36c320170520 709afb07-ca42-40c0-a502-0d4b87ebecc2 a5ae565d-ee9f-4e8d-a606-995ee0170520

You need crash report ID's that start with BP - those three probably weren't submitted to the crash reporting system. Click on each one of those reports to submit them to the "system" and then provide us with the resulting BP- report ID's with the full hyperlink.

from the Unsubmitted Crash Report page, there are a list of Report IDs. I click on the long number, and it goes to Processing Crash Report. After a few seconds, the page title is Crash Reports. That's where I got the above numbers. I don't see any BP, not any other option to submit reports

Did I not do that right? Thanks.

PS. not sure if this helps, but this column was in red: 23 kernelbase.dll kernelbase.dll@0xd585d

At the top there is this:

Firefox 53.0.2 Crash Report [@ std::basic_ostream<T>::write ]

ID: f77668ea-ebb2-44a2-884f-cfea50170520 Signature: std::basic_ostream<T>::write

I do not understand that crash. The red marking can be ignored. The red marking is because a debug symbol is not available. As that is a major Windows file I might have expected it not to be red, however maybe it was recently updated and things have not yet caught up. I checked my own Windows 10 and it has the same version number and GUID string on that dll so I presume it is ok.

One of the other crash reports I could not find so maybe not yet submitted or awaiting processing, the last on is a crash relating to use of FlashPlayer.

The tab crashes with the Gah may be prevented by disabling the multproccess option on Firefox. If your machine is low spec that may help matters. On the oterh hand if it still crashes it will then take down the whole browser not just a single tab.

In fact as I see mention of quite lot of memory. How much RAM have you got ? 16GB ? if so it may be worth you using the 64 bit version of Firefox. That will install separately from the existing 32 bit version. I am not sure it will by default have a separate profile so create a Firefox profile for it then install it without removing the original version.

• Profile Manager - Create, remove or switch Firefox profiles
• How to switch from 32-bit to 64-bit Firefox
  • But do NOT at theis stage uninstall the existing Firefox
  • Later if 64bit Firefox works you may wish to transfer data
    Recovering important data from an old profile_your-important-data-and-their-files

Forum Note Crash reports

• Your crash report for

1. bp-137e41b8-8846-4e23-b120-36c320170520
   • Signature: std::basic_ostream<T>::write
2. bp-a5ae565d-ee9f-4e8d-a606-995ee0170520
   • Signature: F1398665248_____________________________
   • My note and related bug: FlashPLayer related. Long standing Bug 774281 - Generic bug: Flash plugin-container crash in F1398665248

yes, I have 16GB RAM, Intel i76700K, an SSD, gaming graphics card. Have had no issues till a few days ago.

So is the multiprocess likely not a problem with my set-up?

I can try the 64-bit version. Didn't realize I didn't have it.

I had already updated my flash player.

Shall I try to post another crash report? Still not sure how you got that bp number from what I posted..

Thanks.

Multi process Firefox is intended to be big improvement for several reasons, and the number of processes available and used is likely to increase over time, The feature does however have costs and in some cases & with some settings it is worse not better than a single process Firefox. Some background on this:

• 2016 Mozilla Blog : What’s Next for Multi-process Firefox
  https://blog.mozilla.org/futurereleases/2016/08/02/whats-next-for-multi-process-firefox/
  And https://blog.mozilla.org/blog/2016/08/02/exciting-improvements-in-firefox-for-desktop-and-android/

To some extent the 64 bit Firefox is better. It is able to handle much more memory, but again it comes at a cost. If you do not have much RAM it may be better sticking with 32bit Firefox. Linux and Mac s have used 64bit Firefox for a number of years but it has taken a while to sort this out on Windows and until recently Mozilla were not by default offering fully supported 64bit Firefox Releases for Windows users.

As for the mystery bp- numbers, I just searched for the ones that you had posted about upthread,

Ideally Firefox should never crash. FlashPlayer is known to have issues and hopefully will soon not be needed. If you see those tab crashes then it is happening in multi-process Firefox and may not in single process. Firefox.Pre Release versions of Firefox already have better methods of controlling and setting multi-process and performance settings. I do not even have the standard Release on this machine but as far as I know the method to turn multi process on and off is by flipping a pref, rather than having any easy menu type options

Temporarily Disable multi-process tabs in Firefox by setting the related prefs to false on the about:config page.

1. Type in to the address bar about:config & press the [Return]|[Enter] Key
2. Accept any warning.
3. Search for the prefs. Try typing e.au to filter then look for
   browser.tabs.remote.autostart
   browser.tabs.remote.autostart.2
4. Make a note of the original settings found.
5. Select individual preferences and right click, then toggle to false

• Numbers included in pref name may vary due to settings
• See also
  • Ghacks: http://www.ghacks.net/2016/07/22/multi-process-firefox/
  • Our help article: Configuration Editor for Firefox