chromium-browser crashed with signal 5 in gdk_x_error()

Bug #523915 reported by Alex Valavanis
68
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Unknown
Unknown
chromium-browser (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: chromium-browser

Attempted to drag a tab out of Chromium to create a new window. This leads to an unexpected browser crash. This is a deliberate duplicate of previous bugs, to enable me to upload a stacktrace with debug symbols easily.

ProblemType: Crash
Architecture: i386
Date: Thu Feb 18 16:14:29 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
Package: chromium-browser 5.0.307.7~r38400+0-0ubuntu1
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Signal: 5
SourcePackage: chromium-browser
StacktraceTop:
 gdk_x_error (display=0xa3fd338, error=0xbfe504bc)
 _XError (dpy=0xa3fd338, rep=0xacaeb88)
 process_responses (dpy=0xa3fd338,
 _XReply (dpy=0xa3fd338, rep=0xbfe50620, extra=0, discard=1)
 XSync (dpy=0xa3fd338, discard=0) at ../../src/Sync.c:48
Title: chromium-browser crashed with signal 5 in gdk_x_error()
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alex Valavanis (valavanisalex) wrote :
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Confirming (per previous reports)

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gdk_x_error (display=0xa3fd338, error=0xbfe504bc)
 _XError (dpy=0xa3fd338, rep=0xacaeb88)
 process_responses (dpy=0xa3fd338,
 _XReply (dpy=0xa3fd338, rep=0xbfe50620, extra=0, discard=1)
 XSync (dpy=0xa3fd338, discard=0) at ../../src/Sync.c:48

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Attaching a backtrace using --sync command-line option as requested at http://code.google.com/p/chromium/issues/detail?id=36151

Revision history for this message
darvids0n (darvids0n-deactivatedaccount) wrote :

Seems like the resolution for this is to either backport the GTK fix to 2.18.x or bring the base package up to 2.19 series. Doesn't look like a Chromium bug imo, if we're passed a bad xid to our own window then something lower-level has stuffed up.

destombes (dd80869)
Changed in chromium-browser (Ubuntu):
status: Confirmed → Fix Committed
destombes (dd80869)
Changed in chromium-browser (Ubuntu):
status: Fix Committed → Confirmed
Changed in chromium-browser (Ubuntu):
status: Confirmed → Fix Committed
status: Fix Committed → 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.