Anything in the pending folder has not been submitted.

Firefox needs to be online to submit the reports.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

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

Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Press the Reply button. Now go to the reply box and paste them in.

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Some of your crash reports weren’t sent to the Mozilla Servers.

As I said, Firefox doesn't submit my pending report, click opens About Throttling page instead, so I can't submit it, and it is still unsubmitted (it doesn't have "bp-" prefix and is listed in pending reports, not in submitted reports).

I called for more help.

About how long before the browser crashes? What were you and Firefox doing at the time?

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

I don't know how exactly to reproduce it so working in safe mode can take too much time (very awkward work time w/o mouse gestures, customized new tab and other things), therefore I want to submit crash report (which I hope can tell much more than I) and I'm curious why crash feedback is so complicated. I've never sent crash reports before so it is absolutely strange that Firefox tells me about throttling when I'm trying to help.

Can you connect that Firefox to the web?

Are there any Firefox there connected to the web?

Crashes happen in offline account, but there is an online account (w/o access to local servers) which I'm trying to use for submitting crash report copied from offline account.

I usually use pre-release builds so tend not to see the throttling of crash reports.

Try clicking on individual crash reports with luck they may submit when clicked. If not do you have a lot of recently submitted crash reports ? - if you look down the list you may come to some that do have the bp- prefix indicating they were submitted.

There is only one crash report on about:crashes page, the mentioned unsubmitted report, and I see that it is a link that points to the throttling page, so I don't think that clicking it multiple times will produce any effect...

But you have clicked it at least once?

I've clicked it of course, then I've noticed that About Throttling page is just a stub page that doesn't do anything useful. Then I've tried to find another way of submitting a bug report but with no luck, and I'm still not aware of such way.

Bug Report: https://bugzilla.mozilla.org/show_bug.cgi?id=1337267 1337267 about:crashes - all links lead to http://crash ...

On the offline computer, open your file browser to;

Windows: %APPDATA%\Mozilla\Firefox\Crash Reports\pending Win 7/Vista: C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending Win XP/2000: C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Crash Reports\pending

Mac OS: /Users/<username>/Library/Application Support/Firefox/Crash Reports/pending Linux: /home/<username>/.mozilla/firefox/Crash Reports/pending

Copy the most Recent 5-7 File Names in the folder to a thumb drive.

Now plug the thumb drive into a Firefox computer with access to the web. Copy those files to the same folder above. Note: FF should NOT be running.

Start that Firefox. Now try to submit those reports. Once the reports have been submitted, their file names will change.

On the thumb drive, remove the pending file names. Then go into the Crash Reports\submitted folder. All those reports will have this day's date. Move only those files to the thumb. Then plug the thumb back into the off-line FF and copy the reports into this folder;

Windows: %APPDATA%\Mozilla\Firefox\Crash Reports\submitted Win 7/Vista: C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Crash Reports\submitted Win XP/2000: C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Crash Reports\submitted

Mac OS: /Users/<username>/Library/Application Support/Firefox/Crash Reports/submitted Linux: /home/<username>/.mozilla/firefox/Crash Reports/submitted

Once this is done, go back to the Crash Reports\pending folder and delete those files. And post the BP- reports here.

Well, it was just what I've done...

However I've found the problem, it was EFS encryption, online Firefox wasn't able to read this report because it was encrypted by another user account. I've decrypted files and clicked report ID, and online Firefox have finally submitted it!

I think this issue should be considered in case of future similar problems (it would be even better if Firefox could report submission error details like file read errors).

So what is the CrashID please ? Just paste the string; beginning bp- in to a reply and after it is posted the; currently used, old forum software; will convert it to a link.

Mozilla will not want too many Crash reports they are costly to process and multiple reports may be duplicates. You will be exceedingly unlikely to get any response whatsoever (Other than a generic email that does not even link to the report ! ) by just submitting a Crash Report. You or someone else looking at the processed report may gain useful clues to your problem.

CrashID is 4bc822b6-6ce6-41be-8f33-df67b0170519, though it is doesn't matter for this topic. It seems that problem was caused by a recent fix in pipelining processing (because it haven't crashed with previous versions). I've disabled pipelining and it doesn't crash anymore.

bp-4bc822b6-6ce6-41be-8f33-df67b0170519 Signature: mozilla::net::nsHttpConnection::DontReuse

This is for Sumo's Related Bugs 1347856 RESOLVED FIXED Crash in mozilla::net::nsHttpConnection::DontReuse

1337826 RESOLVED FIXED V52 beta 4 under Windows 7 crashes once per hour, was once a week before

Yes, and it seems that one bug was fixed and another one was added...

Sometimes, you need a fix to fix the fix  ;-)