We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted (and Unsubmitted, if any) Crash Reports will appear, similar to the one shown below.
2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

IT HAS TAKEN ME FAR TOO MUCH TIME AND EFFORT TO GATHER THE INFORMATION YOU REQUESTED. I AM TWO BREATHS AWAY FROM DELETING FIREFOX COMPLETELY. THIS IS NOT GOOD CUSTOMER SERVICE BY ANY DEFINITION.

bp-35b95cae-3c95-453c-8728-c55c30260310 bp-b9a3c509-f8b4-43b3-8df2-2ba890260310 bp-6533c963-54cd-4093-bca9-36f8e0260310 bp-6c75e4d2-659b-438e-bd1d-136220260310 bp-95b7a0fe-7d6c-4700-945f-2a8f20260310

It must be a mistake. We don't have any customers. We volunteer our time to answer questions from users, definitely not from customers.

If you are an user, you suffer from out-of-memory crashes. As the first step try to disable your extensions, as Honey and the others can be a reason of this.

Please report back if it helps.

Sorry for that. Please note that the people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers.

Looking at your crash reports, all the crashes seems to have happened because the OS was (almost) out of memory. 4/5 have an explicit OOM (out of memory) signature, and in most cases, the available page file is really small. I'm not sure if there's anything else behind it... So I'd recommend submitting crash reports (and posting here) for any further crashes and monitoring your system memory usage with Windows Task Manager, especially when you suspect that too many things are running.

Oh, and please give a try to TyDraniu's suggestion!