OK, it didn't attach the error...

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

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

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

This is perhaps part of the problem. Not only does it not submit the crashed, but it doesn't know that it didn't submit the crashes.

Digging further, the firefox/Crash Reports folder has a few entries, but is missing the vast majority of the numerous crashes...

However, the lastcrash file exists:

lastcrash: 1443402942

Meanwhile, the submit.log is reporting:

[Sun 27 Sep 2015 04:48:28 PM CDT] Crash report submission failed: Peer certificate cannot be authenticated with known CA certificates [Sun 27 Sep 2015 05:10:30 PM CDT] Crash report submission failed: Peer certificate cannot be authenticated with known CA certificates [Sun 27 Sep 2015 06:03:15 PM CDT] Crash report submission failed: Peer certificate cannot be authenticated with known CA certificates [Sun 27 Sep 2015 08:05:11 PM CDT] Crash report submission failed: Peer certificate cannot be authenticated with known CA certificates [Sun 27 Sep 2015 08:15:49 PM CDT] Crash report submission failed: Peer certificate cannot be authenticated with known CA certificates

The pending folder shows unsubmitted crash reports starting 14-Sept-2015. 118 files = 59 reportable crashes since that time. About 5 per day -- though it seems like they occurred more often than that.

The list for today shows 5, but I think that I had more than that...

Apparently no solutions for this chronic and continuous crashing... The latest Firefox still reports that it CANNOT REPORT crashes and errors.

Oh, and it occurs on multiple machines, so apparently not hardware related...

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options) key, and then starting Firefox. Is the problem still there?

While still in Safe Mode, try the submit the crash reports.

The problem is that "about:crashes" shows no crashes... Apparently crashes before it knows that there is a crash (but it knows that it crashed, because it offers me a chance to submit -- but submission fails every time, so it's in limbo).

Since Firefox randomly crashes (sometimes seconds apart, sometimes days apart...), I don't know if I'll be able to force a crash, but trying "firefox -safe-mode" to see if I can catch something.

Do you have security software that might intercept the connection and send its own certificate?

Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) to see if that helps.

• http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
• http://www.7tutorials.com/4-ways-boot-safe-mode-windows-10

I'm running Linux, with no virus protection

Are you using Linux builds of Firefox from www.mozilla.org/firefox/all or a package build?

I'm running Puppy Linux. I installed a build from Ibiblio, a long time ago (and have simply let it update, as it goes). Something in the recent update has broken something.

It appears that the unreported crashes started on 14-Sept-2015.

I've been pondering uninstalling, and reinstalling an older version, and locking it down to prevent upgrades...

It appears that I had installed a new package at Firefox 24. Since then, it's been auto-updates (which didn't fail until somewhere around V. 39 or 40)

Hmm well crashes reports mainly sent from official builds from mozilla.org and not really third-party builds since Mozilla did not build them.

Prior to September 14th, I never had a problem with Firefox submitting crash reports, on those rare occasions where I had a crash.

As I mentioned, I had installed Firefox 24 -- it worked fine, as did most of those following. Somewhere around version 39 or 40, it started crashing regularly. I'm not sure if that is around the same time that it also started consuming virtually all available RAM, or not (I believe that a few versions earlier were also doing that). It regularly eats between 1.7 and 2.8 GB...

This crashing is a new character -- and I suspect that the problem isn't fixed, because it cannot be reported (see the image I posted above).

Similarly, "about:crashes" shows no crashes -- so I can't force it to submit them, as Firefox somehow doesn't know that they exist (even though it saved them in a folder)...

OK, time for an update. Firefox automagically updated to v.42.0. It promptly exhibited crashes, and still cannot report the crashes (as shown above).

However, it does appear that the frequency of crashes has been reduced -- but it's still not exactly stable... (and the fact that it can't report the crashes may mean that those issues will never be addressed)

You mentioned that crashes happen with multiple Linux computers. All of them running Puppy? Or any other 'flavors' of Linux? Have you tried installing Firefox from Mozilla directly? To get a "genuine" build where the Crash Reporter would / might give us something to read.

Overall, I wonder if part of the Crash Reporting system is disabled in the Linux repository builds, where it works to collect data [or appears to by showing the "We're Sorry" dialog] but doesn't send it to Mozilla. Pure speculation on my part, I have little experience with Linux - one old EeePC Netbook with EasyPeasy [based on Ubuntu] from 2008 that I only use on my home network running Firefox 2.0.0.18.

Previous versions of Firefox were able to report crashes. Firefox updates appear to download a ".mar" file, which seems to do a full overwrite (at least on substantial upgrades). I mean virtually ALL of the previous versions worked fine -- until mid-September, when it stopped working correctly. Puppy version was 24. After that, all new installs were performed by Mozilla.

I was able to "upgrade" to v.20, which operated fine (I downloaded that .mar file, and installed). I then allowed Firefox to upgrade to v.41, after which it began to crash again.

I pulled that version from here:

http://releases.mozilla.org/pub/firefox/releases/

(unfortunately, rolling back broke some of my useful plugins -- wasn't able to find older, compatible versions that I once ran)

I checked with other Puppy users (different starting points -- one guy started with FF 11), who let the upgrade occur, after which they are experiencing crashes.

Another fellow has locked his version at v.37, and is not having trouble.

If this keeps up, I may have to "upgrade" to something like FF portable (v.31).

There are no official builds of portable Firefox for Linux as the build you are thinking of is something somebody made of the old Firefox 31.0 Release that came out July 22, 2014. You would be downgrading to a vulnerable version.

Yes, older versions are vulnerable, and the newer versions are non-functional (since they continually crash). Or is it better to move to Chrome, Safari, Opera or some other stable browser?

On the positive side, I had 9 crashes on Nov 5th (somewhere on the 5th, FF upgraded to v.42). The crash folder only shows 3 crashes since then.

I have 97 crashes since 14-Oct (and that may have been an improvement over previous).

And I show 13 crashes on 01-Nov alone...