[Pkg-chromium-maint] Bug#586387: chromium-browser: Lots of UI crashes and weirdness

Jonathan Nieder jrnieder at gmail.com
Thu Jul 15 04:16:28 UTC 2010

Joe Neal wrote:
> On Wednesday, July 14, 2010 01:08:36 am you wrote:

>>   $ G_DEBUG=fatal_warnings chromium-browser --debug | tee gdb-chromium.txt
>>   (gdb) run
>>   [... browse until it hits a warning ...]
> It doesn't give me a (gdb) prompt so I assume it's nothing to worry about?
> just this:
>> Gdk-WARNING **: XID collision, trouble ahead
>> aborting...
>> [3431:3431:282536897411:ERROR:chrome/browser/tab_contents/tab_contents.cc(1
>> 910)] Not implemented reached in virtual void
>> TabContents::OnCrashedPlugin(const FilePath&) convert plugin path to
>> plugin name

Hmm, my multi-process debugging-fu is not so great.  Maybe --single-process
--plugin-launcher='xterm -e gdb --args' would give a prompt[1].

But the XID collisions are not what I’m interested in; it’s rather the
WebCursor::GetCursorType() calls (that’s what happens before it gets
crashy, right?).

[1] see http://code.google.com/p/chromium/wiki/LinuxDebugging#Plugin_Processes

More information about the Pkg-chromium-maint mailing list