On Mon, Apr 9, 2012 at 12:42 PM, Yuri <[email protected]> wrote: > I attach the log of several such hangs (see file chrome-stack.txt attached > showing which pages are involved).
This is really good! The stacks containing "MessageLoopForUI" are the Chrome user interface thread that communicates with X etc. But in all cases they seem to be stuck in a stack topped by __sys_poll inside glib. Chrome attempts to only call into glib when glib won't block, but it appears to be blocking in glib. There's a bunch of rather subtle logic in this code: http://src.chromium.org/svn/trunk/src/base/message_pump_glib.cc I guess some of it is somehow wrong. :( _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "[email protected]"
