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

Joe Neal vlvtelvis at speakeasy.net
Tue Jul 13 21:39:35 UTC 2010


OK, here's the message printed to stdout when things get crashy:

I was able to catch it in time this time before it kept me from being able to 
copy and past from konsole.

> exe:26007): Gdk-WARNING **: XID collision, trouble ahead
> [25276:25276:174592391385:ERROR:chrome/browser/gtk/tabs/tab_strip_gtk.cc(11
> 56)] Not implemented reached in virtual void
> TabStripGtk::StopAllHighlighting()
> [25276:25276:174606903142:ERROR:chrome/browser/gtk/tabs/tab_strip_gtk.cc(1
> 156)] Not implemented reached in virtual void
> TabStripGtk::StopAllHighlighting()


On Tuesday, July 06, 2010 12:33:12 am Jonathan Nieder wrote:
> Joe Neal wrote:
> > I got it run with chromium frozen.  I just wasn't real sure what to do
> > with the data from there.
> 
> You can copy and paste the backtrace from the terminal or use
> 
>  gdb | tee backtrace.txt
> 
> to log debugging output to a file[1].  Then I would suggest attaching it
> to http://crbug.com/48259 (or failing that, the Debian bug).
> 
> Are there any themes in the backtraces?  Is chromium stuck in a different
> function when frozen than during normal operation?
> 
> Another ignorant question: are you using compiz?  From random searching it
> seems you can temporarily disable compiz by running "kwin --replace"
> if kwin is installed.  I ask because your symptoms seem vaguely
> reminiscent of http://crbug.com/29561
> 
> [1] a trick from http://wiki.debian.org/Chromium/Debugging





More information about the Pkg-chromium-maint mailing list