Sign in to add a comment
|
REGRESSION: chromium-browser crashed with signal 5 in gdk_x_error() | |||||||||||||||||||||||
| Reported by valavani...@gmail.com, Feb 18 2010 | Back to list | |||||||||||||||||||||||
Chrome Version (from the about:version page): 5.0.307.7 (38400+0) Ubuntu Is this the most recent version: yes OS + version: Ubuntu lucid (development branch) CPU architecture (32-bit / 64-bit): 32-bit Window manager: metacity URLs (if relevant): https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/523915 Behavior in Linux Firefox: n/a Behavior in Windows Chrome (if you have access to it): What steps will reproduce the problem? 1. Open a new tab 2. Attempt to drag tab outside Chrome window 3. What is the expected result? A new Chrome window appears, containing the tab What happens instead? Browser crashes Forwarded from Launchpad bug report. Stacktrace and lots of other useful debugging information available there: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/523915
,
Feb 19 2010
For some reason I can't see that bug report. Can you try running with --sync? I tried this with 322.2 and a debug build of ToT I have locally but didn't encounter the error.
,
Feb 19 2010
Hi Evan, the bug is currently marked as private... I have subscribed you to it, so you should be able to view it now. I'll have a go with --sync shortly
,
Feb 19 2010
Can you reproduce this with a current version (dev channel, trunk?).
Important piece the the call stack:
#6 0x00602847 in XSync (dpy=0xa3fd338, discard=0) at ../../src/Sync.c:48
rep = {type = 56 '8', revertTo = 211 '\323', sequenceNumber = 2623,
length = 77596909, focus = 172066952, pad1 = 0, pad2 = 0,
pad3 = 3219457680, pad4 = 2083355, pad5 = 181023024}
#7 0x083c488b in BackingStoreX::PaintToBackingStore (this=0xaca3130,
process=0xa58b708, bitmap=8192032, bitmap_rect=..., copy_rects=...,
painted_synchronously=0xbfe5122e)
at chrome/browser/renderer_host/backing_store_x.cc:348
dib = 0x4a008ef
picture = 77596911
pixmap = 77596909
#8 0x083c28c5 in BackingStoreManager::PrepareBackingStore (host=0xa58aaa0,
backing_store_size=..., bitmap=8192032, bitmap_rect=..., copy_rects=...,
needs_full_paint=0xbfe50f5f, painted_synchronously=0xbfe5122e)
at chrome/browser/renderer_host/backing_store_manager.cc:207
backing_store = <value optimised out>
#9 0x081e7740 in RenderWidgetHost::PaintBackingStoreRect (this=0xa58aaa0,
bitmap=8192032, bitmap_rect=..., copy_rects=..., view_size=...,
painted_synchronously=0xbfe5122e)
at chrome/browser/renderer_host/render_widget_host.cc:904
needs_full_paint = false
CC'ing some people who were in this area recently.
,
Feb 19 2010
Oh, please disregard previous call stack, that is just the point where we sync with
X. The real call stack looks like:
#8 0x00abe0be in XShapeSelectInput () from /usr/lib/libXext.so.6
No symbol table info available.
#9 0x0015d3c7 in free_cache_child (child=0xa5b2428, display=0xa5c7508) at
/build/buildd/gtk+2.0-2.19.5/gdk/x11/gdkdnd-x11.c:327
No locals.
#10 0x003ac7e7 in IA__g_list_foreach (list=0xa79d9a0, func=0x15d360
<free_cache_child>, user_data=0xa5be0b0) at /build/buildd/glib2.0-
2.23.3/glib/glist.c:918
next = 0xa79d990
#11 0x00161680 in gdk_window_cache_destroy (object=0xa5c8150) at
/build/buildd/gtk+2.0-2.19.5/gdk/x11/gdkdnd-x11.c:583
root_window = <value optimised out>
#12 gdk_drag_context_finalize (object=0xa5c8150) at /build/buildd/gtk+2.0-
2.19.5/gdk/x11/gdkdnd-x11.c:198
context = 0xa5c8150
private = 0xa5c8188
tmp_list = 0xa7ad0d0
#13 0x009fd174 in IA__g_object_unref (_object=0xa5c8150) at /build/buildd/glib2.0-
2.23.3/gobject/gobject.c:2484
object = 0xa5c8150
old_ref = 1
__PRETTY_FUNCTION__ = "IA__g_object_unref"
#14 0x01291467 in gtk_drag_source_info_destroy (info=0xae539c0) at
/build/buildd/gtk+2.0-2.19.5/gtk/gtkdnd.c:3992
i = <value optimised out>
#15 0x012959ee in gtk_drag_drop_finished (info=0xae539c0, result=<value optimised
out>, time=254704582) at /build/buildd/gtk+2.0-2.19.5/gtk/gtkdnd.c:3634
success = 1
#16 0x01296232 in gtk_drag_button_release_cb (widget=0xa71b6e8, event=0xb7719630,
data=0xae539c0) at /build/buildd/gtk+2.0-2.19.5/gtk/gtkdnd.c:4373
No locals.
#17 0x01125038 in _gtk_marshal_BOOLEAN__BOXED (closure=0xa614568,
return_value=0xbfc7da84, n_param_values=2, param_values=0xa6f92c8,
invocation_hint=0xbfc7da70, marshal_data=0x12961c0) at /build/buildd/gtk+2.0-
2.19.5/gtk/gtkmarshalers.c:84
data1 = 0xa71b6e8
data2 = 0xae539c0
v_return = <value optimised out>
__PRETTY_FUNCTION__ = "_gtk_marshal_BOOLEAN__BOXED"
#18 0x009fae52 in IA__g_closure_invoke (closure=0xa614568, return_value=0xbfc7da84,
n_param_values=2, param_values=0xa6f92c8, invocation_hint=0xbfc7da70) at
/build/buildd/glib2.0-2.23.3/gobject/gclosure.c:767
marshal = 0x1124f90 <_gtk_marshal_BOOLEAN__BOXED>
marshal_data = 0x0
__PRETTY_FUNCTION__ = "IA__g_closure_invoke"
#19 0x00a10c6d in signal_emit_unlocked_R (node=<value optimised out>, detail=<value
optimised out>, instance=0xa71b6e8, emission_return=0xbfc7dbcc,
instance_and_params=0xa6f92c8) at /build/buildd/glib2.0-2.23.3/gobject/gsignal.c:3243
tmp = <value optimised out>
handler = 0xb7715ce0
accumulator = 0xa5ce7f8
emission = {next = 0x0, instance = 0xa71b6e8, ihint = {signal_id = 34, detail
= 0, run_type = G_SIGNAL_RUN_FIRST}, state = EMISSION_RUN, chain_type = 4}
class_closure = 0xa5ce650
handler_list = <value optimised out>
return_accu = <value optimised out>
accu = {g_type = 20, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0,
v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0,
v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double
= 0, v_pointer = 0x0}}}
signal_id = 34
max_sequential_handler_number = 964
return_value_altered = 0
#20 0x00a12083 in IA__g_signal_emit_valist (instance=0xa71b6e8, signal_id=34,
detail=0, var_args=0xbfc7dc30 "\\\334ǿ\260\364[\n\210\334ǿ
\364\217>\001\350\266q\n0\226q\267x\334ǿ\350\266q\n\350\266q\n\020']\n\004") at
/build/buildd/glib2.0-2.23.3/gobject/gsignal.c:2986
return_value = {g_type = 20, data = {{v_int = 0, v_uint = 0, v_long = 0,
v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0},
{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float =
0, v_double = 0, v_pointer = 0x0}}}
error = <value optimised out>
signal_return_type = 20
node = 0xa5da078
i = <value optimised out>
n_params = 1
__PRETTY_FUNCTION__ = "IA__g_signal_emit_valist"
#21 0x00a126a6 in IA__g_signal_emit (instance=0xa71b6e8, signal_id=34, detail=0) at
/build/buildd/glib2.0-2.23.3/gobject/gsignal.c:3033
No locals.
#22 0x012690ce in gtk_widget_event_internal (widget=<value optimised out>,
event=0xb7719630) at /build/buildd/gtk+2.0-2.19.5/gtk/gtkwidget.c:4949
signal_num = <value optimised out>
return_val = 0
#23 0x0111c3f0 in IA__gtk_propagate_event (widget=0xa71b6e8, event=0xb7719630) at
/build/buildd/gtk+2.0-2.19.5/gtk/gtkmain.c:2447
tmp = 0xa71b6e8
handled_event = <value optimised out>
__PRETTY_FUNCTION__ = "IA__gtk_propagate_event"
#24 0x0111d92f in IA__gtk_main_do_event (event=0xb7719630) at /build/buildd/gtk+2.0-
2.19.5/gtk/gtkmain.c:1647
event_widget = 0xa71b6e8
grab_widget = <value optimised out>
window_group = 0xa5dcf60
rewritten_event = 0x0
tmp_list = <value optimised out>
__PRETTY_FUNCTION__ = "IA__gtk_main_do_event"
#25 0x085a7750 in base::MessagePumpForUI::EventDispatcher (event=0xb7719630,
data=0xa5ec170) at base/message_pump_glib.cc:325
message_pump = 0xa5ec170
#26 0x0016b3ea in gdk_event_dispatch (source=0xa5c7e30, callback=0, user_data=0x0) at
/build/buildd/gtk+2.0-2.19.5/gdk/x11/gdkevents-x11.c:2372
display = <value optimised out>
event = <value optimised out>
#27 0x003aef95 in g_main_dispatch (context=0xa5c7e78) at /build/buildd/glib2.0-
2.23.3/glib/gmain.c:1960
dispatch = 0x16b390 <gdk_event_dispatch>
user_data = 0x0
callback = 0
cb_funcs = 0x0
cb_data = 0x0
current_source_link = {data = 0xa5c7e30, next = 0x0}
source = 0xa5c7e30
current = 0xa5ff710
i = 0
#28 IA__g_main_context_dispatch (context=0xa5c7e78) at /build/buildd/glib2.0-
2.23.3/glib/gmain.c:2513
No locals.
#29 0x003b2c98 in g_main_context_iterate (context=0xa5c7e78, block=<value optimised
out>, dispatch=1, self=0xa59c338) at /build/buildd/glib2.0-2.23.3/glib/gmain.c:2591
max_priority = 2147483647
timeout = 310
some_ready = 1
nfds = <value optimised out>
allocated_nfds = <value optimised out>
fds = <value optimised out>
__PRETTY_FUNCTION__ = "g_main_context_iterate"
#30 0x003b2e58 in IA__g_main_context_iteration (context=0xa5c7e78, may_block=1) at
/build/buildd/glib2.0-2.23.3/glib/gmain.c:2654
retval = <value optimised out>
#31 0x085a7305 in base::MessagePumpForUI::RunWithDispatcher (this=0xa5ec170,
delegate=0xbfc7f2c0, dispatcher=0x0) at base/message_pump_glib.cc:196
state = {delegate = 0xbfc7f2c0, dispatcher = 0x0, should_quit = false,
run_depth = 1, has_work = false}
more_work_is_plausible = <value optimised out>
#32 0x085a6f80 in base::MessagePumpForUI::Run (this=0xa5ec170, delegate=0xbfc7f2c0)
at ./base/message_pump_glib.h:59
No locals.
#33 0x08585165 in MessageLoop::RunInternal (this=0xbfc7f2c0) at
base/message_loop.cc:205
No locals.
#34 0x0858522c in MessageLoop::RunHandler (this=0x0, dispatcher=0x0) at
base/message_loop.cc:177
No locals.
#35 MessageLoopForUI::Run (this=0x0, dispatcher=0x0) at base/message_loop.cc:603
save_state = {<MessageLoop::RunState> = {run_depth = 1, quit_received =
false, dispatcher = 0x0}, loop_ = 0xbfc7f2c0, previous_state_ = 0x0}
,
Feb 19 2010
I installed google-chrome 307.9 and did not encounter this problem either. I am on hardy though. I wonder if something changed in lucid that we're using wrong? (Removing Brett since I don't think this was his change)
,
Feb 19 2010
Tested with dev version (5.0.322.2~r38810+0-0ubuntu1~ucd1)... crash still occurs
,
Feb 19 2010
Tested with daily builds ppa version (5.0.333.0~svn20100219r39418-0ubuntu1~ucd1)... crash still occurs
,
Feb 20 2010
Issue 36332 has been merged into this issue.
,
Feb 20 2010
5.0.334.0 (39541) Ubuntu
$ apt-cache policy chromium-browser
chromium-browser:
Installed: 5.0.334.0~svn20100220r39541-0ubuntu2~ucd1
Candidate: 5.0.334.0~svn20100220r39541-0ubuntu2~ucd1
Version table:
*** 5.0.334.0~svn20100220r39541-0ubuntu2~ucd1 0
500 http://ppa.launchpad.net lucid/main Packages
100 /var/lib/dpkg/status
5.0.307.9~r39052-0ubuntu1 0
500 http://neacm.fe.up.pt lucid/universe Packages
500 http://archive.ubuntu.com lucid/universe Packages
$ chromium-browser --sync
[31220:31220:16320544997:ERROR:chrome/app/chrome_dll_main.cc(231)] Gdk: The program
'chromium-browser' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 78733 error_code 3 request_code 140 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
,
Feb 24 2010
Issue 36365 has been merged into this issue.
,
Feb 24 2010
,
Feb 26 2010
This has always worked fine for me, up to the point I enabled desktop effects in KDE.
,
Feb 27 2010
I can reproduce this on Debian Sid since my last update, on 26th Feb 2010. The workaround is to open multiple chrome windows so that tabs always get dragged to a new chrome window rather than having them create a new window as they are dragged off (which causes the crash). At first the problem only occurred on screen 1 of my dual screen setup but since the first restart after my update it happens consistently everywhere. nvidia drivers.
,
Feb 27 2010
Issue 36981 has been merged into this issue.
,
Feb 28 2010
Issue 37000 has been merged into this issue.
,
Mar 1 2010
Issue 37074 has been merged into this issue.
,
Mar 1 2010
Issue 37024 has been merged into this issue.
,
Mar 3 2010
even the latest release v40515 crashes on my archlinux...
,
Mar 3 2010
I'm also seeing this in Fedora 12 (2.6.31.12-174.2.22.fc12.x86_64): google-chrome-beta-5.0.307.11-39572.x86_64 . This appears to be a regression caused by recent updates to google-chrome. In previous versions, dragging a tab out of the current window and onto the "desktop" would result in a new window; now it crashes the whole browser. IMHO, you can trap errors like these, even BadWindow errors, and handle them gracefully without terminating the application. That way, when some unexpected error happens, or the connection for your remote X-session craps out temporarily, there's a possibility of having the app recover gracefully and not just crash. gnulem-103-~> google-chrome /usr/bin/google-chrome: /lib64/libz.so.1: no version information available (required by /usr/bin/google-chrome) /opt/google/chrome/chrome: /lib64/libz.so.1: no version information available (required by /opt/google/chrome/chrome) [6878:6878:5982943965:ERROR:/usr/local/google/b/slave/chrome-official-linux- 64/build/src/chrome/app/chrome_dll_main.cc(228)] Gdk: The program 'google-chrome' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 15636 error_code 3 request_code 138 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Abort (core dumped) gnulem-104-~> uname -a Linux gnulem 2.6.31.12-174.2.22.fc12.x86_64 #1 SMP Fri Feb 19 18:55:03 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
,
Mar 7 2010
I'm having this exact same issue on my Gentoo amd64 with _self-compiled_ versions of Chromium (from SVN, not ebuilds). It appears to be directly related to gtk+-2.18 as if I install an older version (gtk+-2.16.6) the problem disappears entirely. I've tested 3 times installing both versions of gtk+ and compiling chromium again each time, and all three times it crashes when using gtk+-2.18(gtk+-2.18.7 to be exact).
,
Mar 9 2010
Issue 37741 has been merged into this issue.
,
Mar 9 2010
,
Mar 9 2010
Issue 37114 has been merged into this issue.
,
Mar 10 2010
My current best guess is this is caused by a GTK change. It still can be our bug, of course, but it would help if we could figure out which GTK version introduced the problem. I have GTK 2.18.3 and I don't encounter this problem. If you have a later version of GTK (and don't see it mentioned in the comments already), can you comment with whether this problem affects you? It's easy to reproduce -- just drag a tab off a Chrome window.
,
Mar 10 2010
It crashes with GTK 2.18.7 same as @axllent
,
Mar 10 2010
Oh, I misread that comment. :( Ok, so it was introduced in 2.18.7. Thanks! I'll go look through that now.
,
Mar 10 2010
For those following at home, I found the GTK regression and wrote more notes here: https://bugzilla.gnome.org/show_bug.cgi?id=608615#c5 It is still very possible it is our bug, but if you're the compile-at-home sort you can "git revert da03774c" to work around it for now.
,
Mar 10 2010
^ sorry, that revert suggestion is for GTK, not for Chrome
,
Mar 10 2010
I've also verified it works fine on a fresh install of Fedora 12 with gtk 2.18.3, but breaks when yum upgrades gtk to 2.18.7.
,
Mar 10 2010
Only point that I don't have this problem (GTK+ 2.19.6 here)
,
Mar 10 2010
Yes, they made a fix between 2.19.5 and 2.19.6. So now the question is: do I work around this for people who are in the window of bad GTK versions? I guess so.
,
Mar 10 2010
http://git.gnome.org/browse/gtk+/commit/?id=325cbef27edd58b801509a2016aee6ab6e49d2f1 is the fix by the way. I was thinking to work around in Chrome I could just mask X errors in the troublesome call stack, but the call stack is fully within GTK. :( I'd like to be able to do something other than tell people to downgrade or wait for a new GTK release, but it's not clear we have that option.
,
Mar 10 2010
,
Mar 12 2010
Issue 38049 has been merged into this issue.
,
Mar 12 2010
Issue 38052 has been merged into this issue.
,
Mar 15 2010
For those on Gentoo, this appears to be fixed in gtk+-2.18.7-r1 : http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-libs/gtk+/ChangeLog
,
Mar 18 2010
Issue 38445 has been merged into this issue.
,
Mar 18 2010
This was fixed in on the GTK stable branch in 2.18.8; it appears they're up to GTK 2.18.9 now too, which should also work.
,
Mar 24 2010
Removing mstone-5 label since there's nothing we can do to fix this.
,
Mar 24 2010
I can confirm that upgrading to the (currently) masked x11-libs/gtk+-2.18.9 on Gentoo solves the problem entirely.
,
Mar 25 2010
Just wanted to comment on #34 by evan@chromium.org It might be better evan to not be too worried about bugs which occur across packages and development trees in which bugs that exist in that code will crash your application, updates come very fast and furious in Linux and I don't believe telling people to wait for updates to GTK2 is at all a problem. What is worse in my opinion is trying to work around all of the different package bases which may have bugs.. causing your application to crash, this leads to bloat in an application. If the code works on working versions of GTK2 which do not exhibit bugs in thier GTK2 code, then there is absolutely no problem with NOT working around it. To my knowledge all major versions of Linux distributions release updates in timely manners, and you will run yourself in circles trying to workaround all known bugs outside of your application. Looking at more longer time frame distributions like RHEL and CentOS, they still likewise.. update packages rather quickly. It is probably better to not workaround this if it is a genuine bug in GTK2 and not Chrome browser. Just my 2 cents.
,
Mar 25 2010
Fedora 12's (2.6.32.9-70.fc12.x86_64) latest update, google-chrome-beta-5.0.342.7- 42476.x86_64, still has this bug, as reported above with version google-chrome-beta- 5.0.307.11-39572.x86_64. > ldd /opt/google/chrome/chrome | grep gtk libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00000038f6000000) > rpm -qf /usr/lib64/libgtk-x11-2.0.so.0 gtk2-2.18.7-1.fc12.x86_64 Later versions of these libs are available: http://download.fedora.redhat.com/pub/fedora/linux/updates/testing/12/x86_64/gtk2- 2.18.9-2.fc12.i686.rpm http://download.fedora.redhat.com/pub/fedora/linux/updates/testing/12/x86_64/gtk2- 2.18.9-2.fc12.x86_64.rpm I will test these after I save this message, as test-failure means loss of message :- )
,
Mar 25 2010
https://admin.fedoraproject.org/updates/gtk2-2.18.9-2.fc12 fixes the issue I report above in google-chrome-beta-5.0.342.7-42476.x86_64 : Updating : gtk2-2.18.9-2.fc12.x86_64 1/4 Updating : gtk2-2.18.9-2.fc12.i686 2/4 Cleanup : gtk2-2.18.7-1.fc12 3/4 Cleanup : gtk2-2.18.7-1.fc12 4/4
,
Apr 5 2010
Issue 40394 has been merged into this issue.
,
Apr 5 2010
Issue 40423 has been merged into this issue.
,
Apr 30 2010
,
Jun 21 2010
Realistically, we're not going to work around this. GTK 2.18.7 was a bad release but it was fixed quickly and nobody is stuck with it.
,
Mar 18 2011
Chrome Version (from the about:version page): 5.0.307.7 (38400+0) Ubuntu Is this the most recent version: yes OS + version: Ubuntu lucid (development branch) CPU architecture (32-bit / 64-bit): 32-bit Window manager: metacity URLs (if relevant): https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/523915 Behavior in Linux Firefox: n/a Behavior in Windows Chrome (if you have access to it): What steps will reproduce the problem? 1. Open a new tab 2. Attempt to drag tab outside Chrome window 3. What is the expected result? A new Chrome window appears, containing the tab What happens instead? Browser crashes Forwarded from Launchpad bug report. Stacktrace and lots of other useful debugging information available there: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/523915
,
Mar 19 2011
Chrome Version (from the about:version page): 5.0.307.7 (38400+0) Ubuntu Is this the most recent version: yes OS + version: Ubuntu lucid (development branch) CPU architecture (32-bit / 64-bit): 32-bit Window manager: metacity URLs (if relevant): https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/523915 Behavior in Linux Firefox: n/a Behavior in Windows Chrome (if you have access to it): What steps will reproduce the problem? 1. Open a new tab 2. Attempt to drag tab outside Chrome window 3. What is the expected result? A new Chrome window appears, containing the tab What happens instead? Browser crashes Forwarded from Launchpad bug report. Stacktrace and lots of other useful debugging information available there: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/523915
,
Oct 13 2012
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
,
Mar 9 2013
|
||||||||||||||||||||||||
| ► Sign in to add a comment | ||||||||||||||||||||||||
Confirmed on Ubuntu/Lucid with ToT: [17182:17182:651878761599:ERROR:chrome/app/chrome_dll_main.cc(231)] Gdk: The program 'chromium-browser' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 108003 error_code 3 request_code 140 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. IA__g_logv (log_domain=<value optimized out>, log_level=G_LOG_LEVEL_ERROR, format=0x742ef3 "%s", args1=0xbfffccdc "\310\037\211\n\003") at /build/buildd/glib2.0-2.23.3/glib/gmessages.c:555 555 /build/buildd/glib2.0-2.23.3/glib/gmessages.c: No such file or directory. in /build/buildd/glib2.0-2.23.3/glib/gmessages.c Current language: auto The current source language is "auto; currently c". (gdb) bt #0 IA__g_logv (log_domain=<value optimized out>, log_level=G_LOG_LEVEL_ERROR, format=0x742ef3 "%s", args1=0xbfffccdc "\310\037\211\n\003") at /build/buildd/glib2.0-2.23.3/glib/gmessages.c:555 #1 0x00a4d7f6 in IA__g_log (log_domain=0x72532b "Gdk", log_level=G_LOG_LEVEL_ERROR, format=0x742ef3 "%s") at /build/buildd/glib2.0-2.23.3/glib/gmessages.c:569 #2 0x0070ddf1 in gdk_x_error (display=0xa2d8368, error=0xbfffcdac) at /build/buildd/gtk+2.0-2.19.5/gdk/x11/gdkmain-x11.c:466 #3 0x00185299 in _XError (dpy=0xa2d8368, rep=0xa838bd0) at ../../src/XlibInt.c:3103 #4 0x0018b92f in process_responses (dpy=0xa2d8368, wait_for_first_event=<value optimized out>, current_error=0xbfffcedc, current_request=108006) at ../../src/xcb_io.c:214 #5 0x0018bfb6 in _XReply (dpy=0xa2d8368, rep=0xbfffcf10, extra=0, discard=1) at ../../src/xcb_io.c:464 #6 0x00181211 in XTranslateCoordinates (dpy=0xa2d8368, src_win=94395805, dest_win=322, src_x=4, src_y=78, dst_x=0xbfffcf78, dst_y=0xbfffcf74, child=0xbfffcf7c) at ../../src/TrCoords.c:53 #7 0x00718dab in gdk_window_x11_get_root_coords (window=0xaf72d40, x=4, y=78, root_x=0xbfffd00c, root_y=0xbfffd008) at /build/buildd/gtk+2.0- 2.19.5/gdk/x11/gdkwindow-x11.c:2814 #8 0x006e10a8 in IA__gdk_window_get_origin (window=0xaf72d40, x=0xbfffd00c, y=0xbfffd008) at /build/buildd/gtk+2.0-2.19.5/gdk/gdkwindow.c:8029 #9 0x08262a1d in TabContentsViewGtk::GetContainerBounds (this=0xad040c0, out=0xbfffd268) at chrome/browser/tab_contents/tab_contents_view_gtk.cc:225 #10 0x080ee7d3 in TabContentsView::GetContainerSize (this=0xaf495c0, size=0xbfffd2b8) at ./chrome/browser/tab_contents/tab_contents_view.h:71 #11 BookmarkBarGtk::GetTabContentsSize (this=0xaf495c0, size=0xbfffd2b8) at chrome/browser/gtk/bookmark_bar_gtk.cc:699 #12 0x080ee927 in BookmarkBarGtk::PaintEventBox (this=0xaf495c0) at chrome/browser/gtk/bookmark_bar_gtk.cc:677 #13 0x085c9079 in MessageLoop::RunTask (this=0xbfffe850, task=0xacb00b0) at base/message_loop.cc:320 #14 0x085c9246 in MessageLoop::DeferOrRunPendingTask (this=0xbfffe850, pending_task=...) at base/message_loop.cc:328 #15 0x085c94dc in MessageLoop::DoWork (this=0xbfffe850) at base/message_loop.cc:435 #16 0x085e7c6a in base::MessagePumpForUI::RunWithDispatcher (this=0xa319f98, delegate=0xbfffe850, dispatcher=0x0) at base/message_pump_glib.cc:199 #17 0x085e78d0 in base::MessagePumpForUI::Run (this=0xa319f98, delegate=0xbfffe850) at ./base/message_pump_glib.h:59 #18 0x085c8335 in MessageLoop::RunInternal (this=0xbfffe850) at base/message_loop.cc:205 #19 0x085c83fc in MessageLoop::RunHandler (this=0x0, dispatcher=0x0) at base/message_loop.cc:177 #20 MessageLoopForUI::Run (this=0x0, dispatcher=0x0) at base/message_loop.cc:603 #21 0x0806d838 in RunUIMessageLoop (browser_process=<value optimized out>) at chrome/browser/browser_main.cc:164 #22 0x0806fb5e in BrowserMain (parameters=...) at chrome/browser/browser_main.cc:993 #23 0x0806ab0f in ChromeMain (argc=3, argv=0xbffff824) at chrome/app/chrome_dll_main.cc:756 #24 0x0806afa5 in main (argc=3, argv=0xbffff824) at chrome/app/chrome_exe_main_gtk.cc:52