Date: Mon, 9 Apr 2012 13:03:29 -0700 From: Evan Martin <evan@chromium.org> To: Yuri <yuri@rawbw.com> Cc: chromium@freebsd.org Subject: Re: chromium-16.0.912.77: gui freezes when waiting for network Message-ID: <CAFzwtj1C-913uXq9NrgeqEjfEPn92i2Q9jUd_Ujg77fyRC=J4g@mail.gmail.com> In-Reply-To: <4F833BAE.90700@rawbw.com> References: <4F320301.6090403@rawbw.com> <CAFzwtj3AV18oXWqvtDdZt%2B29iTG_oFxpbz_33Vz0Uy=ox2y4pQ@mail.gmail.com> <4F833BAE.90700@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 9, 2012 at 12:42 PM, Yuri <yuri@rawbw.com> 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. :(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFzwtj1C-913uXq9NrgeqEjfEPn92i2Q9jUd_Ujg77fyRC=J4g>