Date: Tue, 17 Apr 2012 10:10:26 -0700 From: Yuri <yuri@rawbw.com> To: Evan Martin <evan@chromium.org> Cc: chromium@freebsd.org Subject: Re: chromium-16.0.912.77: gui freezes when waiting for network Message-ID: <4F8DA402.2020803@rawbw.com> In-Reply-To: <CAFzwtj1C-913uXq9NrgeqEjfEPn92i2Q9jUd_Ujg77fyRC=J4g@mail.gmail.com> References: <4F320301.6090403@rawbw.com> <CAFzwtj3AV18oXWqvtDdZt%2B29iTG_oFxpbz_33Vz0Uy=ox2y4pQ@mail.gmail.com> <4F833BAE.90700@rawbw.com> <CAFzwtj1C-913uXq9NrgeqEjfEPn92i2Q9jUd_Ujg77fyRC=J4g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/09/2012 13:03, Evan Martin wrote: > 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.:( This issue is completely fixed in 18.0.1025.162. Thanks! Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F8DA402.2020803>