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/Unsubmitted 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.

edited ::

Any update on this?

Your example HTML file loads for me without crashing.

Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile. Make sure you stay signed out of your sync account when testing.

Your example HTML file loads for me without crashing. Does it still happen in a new profile? An easy way to test a new profile is to install Developer Edition and see if it happens there or refresh your existing profile. Make sure you stay signed out of your sync account when testing.

It doesn't happen in new profile. So it seems like there's something wrong with my current profile.

I've tried disabling all addons and extensions, and then restarted with Add-ons disabled, but the problem persists when using my current profile.

I think I'm just gonna ignore this minor issue, it's too troublesome if I have to create a fresh profile.

Thanks for the help.

To identify the issue, you would need to backup your profile folder and remove the prefs.js file (while the browser is not running) to see if an about:config setting is responsible.

Tysm for your help. Just like you said, it was caused by an about:config setting.

Problem solved by resetting the value of network.buffer.cache.size to default.