firefox-granparadiso crashed (/w cairo assert)

Bug #122735 reported by Shirish Agarwal
2
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Fix Released
Medium
Mozilla Bugs

Bug Description

Binary package hint: firefox-granparadiso

... firefox-granparadiso crashes with new profile

create a new profile with firefox-granparadiso 3.0~alpha5-0ubuntu2 using firefox-granparadiso --profilemanager & nothing is in use . Firefox crashes giving the following error.

shirish@ubuntu:~$ firefox-granparadiso --profilemanager

***MEMORY-WARNING***: firefox-granparadiso-bin[7335]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
firefox-granparadiso-bin: /build/buildd/libcairo-1.4.8/src/cairo-hash.c:196: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.
Aborted (core dumped)

libcairo2 version is 1.4.8-1

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote : Report Needed

Thank you Shirish Agarwal for submitting this report.

Could you please try to obtain a backtrace by following the instructions
on [1], or upload the crash report that probably was generated during
the crash and that should be located at /var/crash/ to [2].

Please indicate which extensions/plugins do you have enabled; and if
this crash is reproducible describe the steps that lead to it (it is
very important for us to have a test case for each crash).

This will greatly aid us in tracking down your problem.

Thanks in advance.

H. Montoliu

[1] https://wiki.ubuntu.com/MozillaTeam/Bugs
[2] https://bugs.launchpad.net/ubuntu/+source/firefox-granparadiso/+bug/122735/+addcomment

description: updated
Changed in firefox-granparadiso:
assignee: nobody → mozilla-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Shirish Agarwal (shirishag75) wrote : Re: firefox-granparadiso crashed

I think you better close this down for the moment, for before I was able to reproduce it but after installing the -dbgsym I'm unable to get this reproduced. I do have Adblock Plus extension enabled. Another thing though which I observed is after I have exited from File > Quit or X above it does not give back the CLI control. I have to invariably do a CTRL^C which gives me back the CLI. If you think either of these things need some more investigation please lemme know.

Revision history for this message
Hilario J. Montoliu (hjmf) (hmontoliu) wrote :

Thank you for your feedback,

we are closing now this report, please, reopen it at any time if you have more related info.

> Another thing though which I observed is after I have exited from File > Quit or X above it does not give back the CLI control. I have to invariably do a CTRL^C which gives me back the CLI

That might deserve another bug report. Please check that it happens always and fill up a new report so that issue can have the right visibility.

Thanks in advance.

H. Montoliu

Changed in firefox-granparadiso:
status: Incomplete → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

reopening ... this crash is an assertion and happens if you link paradiso against vanilla cairo. Mozilla's in source cairo is a patched one that makes all assertions non-fatal.

Changed in firefox-granparadiso:
status: Invalid → Confirmed
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

Is this still an issue with more recent versions of firefox-3.0?

Changed in firefox-granparadiso:
status: Confirmed → Incomplete
Revision history for this message
Shirish Agarwal (shirishag75) wrote :

I have no idea if this is still an issue or not for I don't know if asac has linked or de-linked vanilla cairo or not. As far as firefox crashes are concerned, they have definitely become less, but due to what I'm not sure.

Revision history for this message
Alexander Sack (asac) wrote :

we haven't received any duplicates for some time. I guess this has been fixed in the meantime.

Changed in firefox-3.0:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.