firefox-3.0 crashed with SIGSEGV in IA__gtk_widget_queue_draw_area

Bug #187878 reported by RobotII
32
This bug affects 2 people
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: firefox-3.0

Run firefox 3, did a bit of browsing then left it open in the background.
Whilst working in Tomboy, switched back to firefox, then it crashed.
Cannot reproduce unfortunately.

ProblemType: Crash
Architecture: i386
Date: Thu Jan 31 22:13:59 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0-3.0b3pre/firefox-3.0
NonfreeKernelModules: cdrom
Package: firefox-3.0 3.0~b3~cvs20080101t1000+nobinonly-0ubuntu1 [modified: usr/lib/firefox-3.0-3.0b3pre/firefox-3.0]
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox-3.0-3.0b3pre/firefox-3.0
ProcCwd: /home/petera
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: firefox-3.0
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libpthread.so.0
 ?? () from /usr/lib/xulrunner-1.9b3pre/libxul.so
 ?? ()
 ?? ()
Title: firefox-3.0 crashed with SIGSEGV in __kernel_vsyscall()
Uname: Linux holly 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
RobotII (pete-arthur) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__gtk_widget_queue_draw_area (widget=0x8e1b190, x=0, y=0, width=160, height=300)
IA__gtk_widget_queue_draw (widget=0x8e1b190)
gtk_window_on_composited_changed (screen=0x8081100, window=0x8e1b190)
IA__g_cclosure_marshal_VOID__VOID (closure=0xa3a4100, return_value=0x0, n_param_values=1,
IA__g_closure_invoke (closure=0xa3a4100, return_value=0x0, n_param_values=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in firefox-3.0:
importance: Undecided → Medium
Revision history for this message
Alexander Sack (asac) wrote :

as you cannot reproduce, we are now waiting for a duplicate before looking closer.

Changed in firefox-3.0:
status: New → Incomplete
Revision history for this message
Basilio Kublik (sourcercito) 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 firefox-3.0:
status: Incomplete → Invalid
Revision history for this message
Viorel Cernăţeanu (vrilutza) wrote :

Hi, I confirm this bug with all day to update - Intrepid Ibex Alpha 6

Revision history for this message
Viorel Cernăţeanu (vrilutza) wrote :
Revision history for this message
MartinB (martin-burman) wrote :

Like said earlier:
Run firefox 3, did a bit of browsing then left it open in the background.
Whilst working in CompizConfig Settings, switched back to firefox, then it crashed.
Cannot reproduce unfortunately.

Hint: System originally at Ubuntu version 6.xx (04?), added Beryl in 7.xx and the system feels a bit "dirty" at the moment whith X crashing every time i login into X first time, second time it always works.

Made Compiz work whith blanking out LD_LIBRARY_PATH.

Revision history for this message
Christian Glodt (cglodt) wrote :

I had the same crash today (on jaunty). I'm using metacity with its compositor.
Sometimes metacity develops a problem where it doesn't display the panel and awn any more.
I restart it by pressing Alt-F2 and running "metacity --replace". This involves compositing
being switched off and on again, which explains why gtk_window_on_composited_changed
turns up in the stack trace.

It seems firefox doesn't always handle compositing being switched on or off well.

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.