Open Bug 1392014 Opened 2 years ago Updated Last year

GLib-GObject-CRITICAL starting Firefox

Categories

(Core :: Widget: Gtk, defect, P2)

55 Branch
All
Linux
defect

Tracking

()

UNCONFIRMED

People

(Reporter: ToddAndMargo, Unassigned)

Details

(Whiteboard: [Scientific Linux 7.3])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build ID: 20170810000947

Steps to reproduce:

Dear Mozilla,

Would one of our intrepid heroes please fix this for me?

Scientific Linux 7.3 (RHEL Clone , re-branded CentOS)
firefox-55.0.2.x64.tar.bz2   (version does not matter)
$ cat /etc/redhat-release: Scientific Linux release 7.3 (Nitrogen)
uname -r: 3.10.0-693.1.1.el7.x86_64

I just ran an update on Scientific Linux 7.3 and the Firefox binary will no longer start.  This includes safe mode, the profile manager, and renaming .moziila to force a fresh profile. Firefox goes straight through to the crash reporter.

This happens with each versions of the binary I tried.

Running ff from the command line gives:

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

        ExceptionHandler::GenerateDump cloned child 20002

Many thanks,
-T


This is the entire run line:

$ /usr/lib64/firefox-55.0.2/firefox
1502915187828   addons.xpi      WARN    Add-on bibletoolbar@bibletoolbar.net is not correctly signed.
1502915187834   addons.xpi      WARN    Add-on bibletoolbar@bibletoolbar.net is not correctly signed.
1502915188302   addons.webextension.<unknown>   WARN    Loading extension 'null': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page.
1502915188339   addons.webextension.<unknown>   WARN    Loading extension 'null': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest.
1502915188339   addons.webextension.<unknown>   WARN    Loading extension 'null': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest.
1502915188719   addons.xpi      WARN    Add-on {1BC9BA34-1EED-42ca-A505-6D2F1A935BBB} is not correctly signed.
1502915188726   addons.xpi      WARN    Add-on {1BC9BA34-1EED-42ca-A505-6D2F1A935BBB} is not correctly signed.

(firefox:19909): GLib-GObject-CRITICAL **: g_object_ref: assertion 'object->ref_count > 0' failed
ExceptionHandler::GenerateDump cloned child 20002
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Component: Untriaged → Widget: Gtk
Product: Firefox → Core
As a test, I tried the same thing under Fedora 26 Xfce 4.12.  I worked perfectly.  :'(

Yo can probably troubleshoot this by making a Live USB from one of these:
http://ftp1.scientificlinux.org/linux/scientific/7x/x86_64/iso/

The gNome one would be closer to Xfce than the KDE one.
OS: Unspecified → Linux
Priority: -- → P2
Hardware: Unspecified → All
Whiteboard: [Scientific Linux 7.3]
No symptom change under Scientific Linux 7.4
Now that 57 has hit, I really need to be able to see what my customers are seeing.  Is there any chance of you guys working on this any time soon?
(In reply to Todd from comment #0)
> (firefox:19909): GLib-GObject-CRITICAL **: g_object_ref: assertion
> 'object->ref_count > 0' failed

I'm pretty sure this is unrelated. I see that message all the time while running Firefox, and it doesn't prevent Firefox from starting or working properly.

> the Firefox binary will no longer start [...] Firefox goes straight 
> through to the crash reporter.

The first step to diagnosing the problem is to locate the crash report which contains various details about the crash (most importantly, the stack trace).

I'm assuming you submitted the crash using the crash reporter? (If not please do so.)

The usual way to locate a submitted crash report is to go to "about:crashes" in Firefox, but since you can't start Firefox, we have to do it a bit more manually.

Does the following directory exist on your system:

  $HOME/.mozilla/firefox/Crash Reports/submitted

Is there a file in there whose timestamp matches a crash? If so, please post the name of the file, which identifies the crash report.
You should have available Firefox 60.1.0 for RHEL7 now.
You need to log in before you can comment on or make changes to this bug.