This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Firefox crashes at startup continuously

  • 6 răspunsuri
  • 3 au această problemă
  • 1 vizualizare
  • Ultimul răspuns de BradleySmall

more options

Crash ID: bp-348bfa65-a5d9-42ef-97ae-f23ec0170710

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

This started happening after letting machine battery die. Since restarting firefox will only start with the report error dialog. I have removed and purged and reinstalled firefox-esr. Does same thing in safe-mode.

firefox-esr:

 Installed: 52.2.0esr-1~deb8u1
 Candidate: 52.2.0esr-1~deb8u1

uname -a Linux myHostName 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.30-2~bpo8+1 (2017-06-14) x86_64 GNU/Linux

Crash ID: bp-348bfa65-a5d9-42ef-97ae-f23ec0170710 (firefox-esr:23430): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed ExceptionHandler::GenerateDump cloned child 23449 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... This started happening after letting machine battery die. Since restarting firefox will only start with the report error dialog. I have removed and purged and reinstalled firefox-esr. Does same thing in safe-mode. firefox-esr: Installed: 52.2.0esr-1~deb8u1 Candidate: 52.2.0esr-1~deb8u1 uname -a Linux myHostName 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.30-2~bpo8+1 (2017-06-14) x86_64 GNU/Linux

Toate răspunsurile (6)

more options

If you haven't already, could you try starting up in the Profile Manager and creating a new profile (e.g., July2017) to see whether this is a problem in your existing profile? See: Profile Manager - Create, remove or switch Firefox profiles. (Please do not delete any existing profiles, it's too easy to delete the wrong one.)

Also, does your OS have any kind of "repair" feature you could use to verify that the system files are undamaged/uncorrupted?

more options

I went so far as to have someone else login with their profile on this machine and it behaved the same way for him.

I have removed/purged the whole of firefox and firefox-esr as well and reinstalled Firefox-esr only.

Behavior is unchanged.

more options

Will Firefox even start up in the Profile Manager or can you not even get to that dialog?

When Firefox crashes, are you getting the Mozilla Crash Reporter form? Your Firefox may have logged some data that would help track down the cause of the problem. If Firefox was able to submit the form data to Mozilla, you can share it with forum volunteers by providing the crash report ID(s). Please check the support article "Firefox crashes - asking for support" for steps to get those crash report IDs from the about:crashes page or from disk. If the site doesn't show Linux-specific steps, use the Editing Tools section in the left column to switch the OS.

more options

Yes, all I get is the Crash Reporter form. When I open the file it makes I get the crash number which I posted in the first post. On the command line I get the messages that I also posted in the first post.

I have since removed my QT-Curve theme from both Application Appearance and Workspace Appearance.

I have since downgraded to Firefox-esr 45.9.0 and I am able to run that successfully. Except that my package manager things there is an upgrade to 52.2.0 available to me :)

more options

I wasn't sure whether you would have gotten the same errors after using a new profile.

At least you have a workaround for the moment.

I'm a Windows person. Hopefully a volunteer who uses Linux can better interpret the crash report and command line error.

more options

Thanks for trying. And, yes, hopefully one will.