chromium-browser crashed with SIGSEGV in IA__gdk_x11_window_get_drawable_impl()

Bug #1015430 reported by Dmitry Shachnev
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Seems similar to bug 652481, but that one is quite old...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic i686
ApportVersion: 2.0.1-0ubuntu9
Architecture: i386
Date: Wed Jun 13 12:44:48 2012
Desktop-Session:
 DESKTOP_SESSION = gnome-fallback
 XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome-fallback:/etc/xdg
 XDG_DATA_DIRS = /usr/share/gnome-fallback:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
ExecutableTimestamp: 1335856200
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ https://mail.google.com/mail/
ProcCwd: /home/mandriver
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xcbf974 <gdk_x11_window_get_drawable_impl+4>: mov 0xc(%eax),%eax
 PC (0x00cbf974) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 gdk_x11_window_get_drawable_impl () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
Title: chromium-browser crashed with SIGSEGV in gdk_x11_window_get_drawable_impl()
UpgradeStatus: Upgraded to precise on 2012-02-09 (124 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev nopasswdlogin plugdev sambashare tape video
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Dmitry Shachnev (mitya57) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 IA__gdk_x11_window_get_drawable_impl (window=0x0) at /build/buildd/gtk+2.0-2.24.10/gdk/x11/gdkdrawable-x11.c:962
 ungrab_dnd_keys (widget=<optimized out>, time=<optimized out>) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkdnd.c:506
 gtk_drag_release_ipc_widget (widget=<optimized out>) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkdnd.c:552
 gtk_drag_selection_received (widget=0xb999b0b8, selection_data=0xbfeb3904, time=411766, data=0xb919f000) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkdnd.c:1813
 _gtk_marshal_VOID__BOXED_UINT (closure=0xb91852e0, return_value=0x0, n_param_values=3, param_values=0xbfeb3650, invocation_hint=0xbfeb35d0, marshal_data=0x0) at /build/buildd/gtk+2.0-2.24.10/gtk/gtkmarshalers.c:1463

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
summary: chromium-browser crashed with SIGSEGV in
- gdk_x11_window_get_drawable_impl()
+ IA__gdk_x11_window_get_drawable_impl()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Edward Donovan (edward.donovan) wrote :

My case, presuming it's a dupe, happened when I dragged the site icon to the tab bar, trying to open another tab with it. Got a long delay, then a crash.

Thanks.

Revision history for this message
Michał Sawicz (saviq) wrote :

For me as well, this happened when trying to drag a url onto a tab in chromium.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Closing now as this report wasn’t investigated timely and is now too old to be meaningful.
Please do not hesitate to report crashes occurring with recent releases of chromium-browser, they will hopefully be investigated and acted upon in a more timely manner.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Won't Fix
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.