epiphany-gecko crashed with SIGSEGV in g_closure_invoke()

Bug #305810 reported by Fabri Velas
4
Affects Status Importance Assigned to Milestone
xulrunner-1.9 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: epiphany-browser

Description: Ubuntu 8.10
Release: 8.10
 *** 2.24.1-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages

Epiphany crashed while opening several blog entries as tabs.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/epiphany-gecko
Package: epiphany-gecko 2.24.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: epiphany-browser
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_BE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: epiphany-browser
StacktraceTop:
 ?? () from /usr/lib/xulrunner-1.9.0.4/libxul.so
 ?? () from /usr/lib/xulrunner-1.9.0.4/libxul.so
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: epiphany-gecko crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.27-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Fabri Velas (fabrivelas) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
_gtk_marshal_BOOLEAN__BOXED (closure=0x9d539e0,
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in epiphany-browser:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash is a libxul one

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in xulrunner-1.9 (Ubuntu):
status: Incomplete → Invalid
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.