Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox crashes

  • 13 replies
  • 1 has this problem
  • 34 views
  • Last reply by Pogo1

more options

Firefox had a problem and crashed.

Unfortunately, the crash reporter is unable to submit a crash report.

Details: Couldn't move crash dump.

Firefox had a problem and crashed. Unfortunately, the crash reporter is unable to submit a crash report. Details: Couldn't move crash dump.

All Replies (13)

more options
more options

I can't do any of that because firefox won't open. I get a crash report weinow with the text quoted above. No option but to close. I get the same result trying to run in safe mode.

This happened immediately after updating Firefox under Ubuntu 14.04 running un a crouton on a Chromebook.

more options
more options

A change, in that the crash reporter was able to report the crash, but firefox still crashed.

more options

Please see this support article: https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

Instructions there about retrieving Crash Report ID's even if Firefox won't launch or won't run.

more options

Try the Firefox version from the official Mozilla server if you currently use a version from the repositories of your Linux distribution.

more options

Thanks. I tried that first. The the file downloaded and unpacked, but I couldn't make it run, neither the scripts nor the executable. The scripts fell through to the "cant run..." error message. The executable just failed silently. I checked the permissions and they seemed ok. Then I was stuck.

more options

Try to start Firefox via a terminal window to see if that display error messages.

more options
more options

Where is the crash report ? the-edmeister gave you a URL with directions on how to message back the bp- URL

more options

So he did. and if I had a working browser, then I couls have followed the link, but then if I had a working browser, I wouldn't be here.

The cut down browser that I do have does not line wrap, so long replies disappear. It seems to run its own cut and paste buffer. My copy of the terminal output was dumped in favour of a long URL (which disappeares off the right side of the screen).

Here is what I found in ~/.mozilla/firefox/Crash Reports/submitted: bp-e50fcda7-6287-4a56-ae4e-801ab0171219.txt

And here is the content of that file: Crash ID: bp-e50fcda7-6287-4a56-ae4e-801ab0171219

Both copied by hand, so possibly in error, but they seem to be the same.

The contents of the terminal output are just way too much to type reliably.

more options

What I meant was messages that appear in the console after you started Firefox via the console.

The crash report you posted doesn't have symbols, so we only see addresses and not a link to the Firefox source code.

I also see ARM as the architecture (armv7l), so I assume that this is a special build that runs on a mobile device. Maybe you should contact Ubuntu for support if this is not an official build.

more options

Back from Christmas. I hope that you all had a good break away.

I am running firefox in a crouton that runs Ubuntu 14.04 on a Samsung Chromebook. It has an ARM processor.

This is what appears in the terminal when firefox crashes:

(trusty)pogo@localhost:~$ firefox

(firefox:10533): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(firefox:10533): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed

(firefox:10533): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(firefox:10533): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed

(firefox:10533): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(firefox:10533): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed ExceptionHandler::GenerateDump cloned child 10604 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...

(/usr/lib/firefox/firefox:10586): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(/usr/lib/firefox/firefox:10586): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed

(/usr/lib/firefox/firefox:10586): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(/usr/lib/firefox/firefox:10586): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed

(/usr/lib/firefox/firefox:10586): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed

(/usr/lib/firefox/firefox:10586): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed


I've got another browser (Midori) running, so I can and have been following the links provided. So far nothing helpful.

I have found a 3k file in the pending folder that looks like a startup log but there is no way to attach it.

At worst I can reinstall the crouton which will probably reinstall the older version of firefox.