ports/161737: chromium 14.0.835.x stalls (probably
rene at freebsd.org
Mon Jan 2 13:36:03 UTC 2012
2011/12/15 Luigi Rizzo <luigi at onelab2.iet.unipi.it>:
> On Wed, Dec 14, 2011 at 11:12:22PM +0100, Rene Ladan wrote:
>> On 17-10-2011 13:41, Luigi Rizzo wrote:
>> >> Number: 161737
>> >> Category: ports
>> > On both of my RELENG_8 machines, since i updated
>> > from chromium 13.0.782.112 to 14.0.835.* I am experiencing
>> > frequent stalls on most pages -- from gmail to google docs to
>> > online forms for accessing various services, after a
>> > short time the tab containing the page become insensitive to
>> > keyboard and mouse input events for large amount of times
>> > (from 30s to minutes) before processing them.
>> > This does not affect just input: on some other sites
>> > i am seeing mouse clicks being only partially
>> > processed, i.e. the click causes part of the content to
>> > be updated, but another part remain stale.
>> > I am seeing this in particular on JS-based pages (99.99% these days).
>> > Unfortunately this makes chromium unusable for services where
>> > i cannot tolerate crashing the tab in the middle of a transaction
>> > (bank, shops, reservations etc.)
>> > Haven't done a deep investigation, but it worked fine with
>> > 13.0.782.112 and broke when i updated to 14.0.835.X (both versions).
>> > The commit logs show some changes
>> > (tcmalloc, v8) that might be related to what i am seeing.
>> >> How-To-Repeat:
>> > open a spreadsheet in google docs, play with it for a while,
>> > until you'll see that keypresses and clicks are not
>> > processed anymore.
>> Can you try with chromium 16.0.912.63 ?
> i think this PR can be closed.
> Things seem to have improved with
> chromium-15.0.874.121 and i forgot about the PR.
> Now building 16.0.X
Can you confirm that it works with chromium 16 and that this PR can be closed?
More information about the freebsd-chromium