The good news is that I have experienced no browser crashes in the last three weeks. That is great, although, I have no idea why they stopped. The disturbing thing is that no one was able to help me overcome the complete suppression of crash reports submitted by me from my Firefox. I think I should be allowed to submit crash reports. McCoy, thanks, I guess, for the above links, but they are way above my level of technical understanding. Bottom line - no effective help received, but problem went away. Crash reporting still broken.

Hi,

To clarify, the "throttling" of crashes happens because Mozilla gets so many crash reports (Firefox has hundreds of millions of users, even if the browser crashes a tiny fraction of the time that results in a lot of crashes) that it's difficult to process them all. As a result, only a certain percentage of crashes are submitted automatically.

However, you can still submit crashes yourself. If you type "about:crashes" in the address bar, you'll see two sections: "unsubmitted" and "submitted". Next to each of the "unsubmitted" reports, there should be a "submit" button. If you click that, and then reload the page, the report will show up in the submitted section. From there, you can click the "view" link to get a link that you can share here.

Regarding your original issue, if this issue returns, you might want to try installing an ad-blocking extension, like uBlock origin: https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/. The reason I mention this is that I tried leaving an article on that site open for a while, and sometimes the ads on that page would keep loading forever, using more and more and more resources and causing the page to run slowly. Eventually, the tab used up all of the available memory on my computer, causing the tab to crash. It's possible that that's the cause of the crash you are experiencing.

Hope that helps!

Thanks for the advice about ads causing the crashes. "However, you can still submit crashes yourself." Yeah, accept that doesn't work.

Crash reports are throttled when you send too many reports with the same signature. In such a case it doesn't make much sense because it doesn't add new information, it is enough to update a counter in such a case (I don't know if this is actually done). If there are new crashes with a different signature then you should be able to send a report.