Date: Sat, 11 Jul 2015 21:57:42 +0100 From: Miguel C <miguelmclara@gmail.com> To: Colin Percival <cperciva@freebsd.org> Cc: Konstantin Belousov <kostikbel@gmail.com>, chromium-list freebsd <freebsd-chromium@freebsd.org> Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] Message-ID: <CADGo8CXFE-Kxpgh7hL1c0DrzZ6L6B8ZNE_rC0_CHp97PGx33BQ@mail.gmail.com> In-Reply-To: <55A17EAC.1000604@freebsd.org> References: <201410051736.s95Ha0U7010634@svn.freebsd.org> <55A08F18.7060803@freebsd.org> <20150711112654.GC2080@kib.kiev.ua> <55A17EAC.1000604@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I am at least :| Was just using chrome and wondering WT...H was wrong and just saw the email. If important: FreeBSD r2d2 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r285207+284d3e5(master) --> chromium-43.0.2357.130 Not sure what triggers it... happens randomly opening new tabs from links (new empty tab seems to work fine all the time) :| Melhores Cumprimentos // Best Regards ----------------------------------------------- Miguel Clara IT - Sys Admin & Developer On Sat, Jul 11, 2015 at 9:38 PM, Colin Percival <cperciva@freebsd.org> wrote: > On 07/11/15 04:26, Konstantin Belousov wrote: >> On Fri, Jul 10, 2015 at 08:35:52PM -0700, Colin Percival wrote: >>> Is anyone else seeing the 100%-CPU-usage chrome problem? It seems to >>> be triggered by a crashing chrome rendering process, and I don't know >>> what's causing that, so it's possible that this isn't affecting many >>> other people. >>> >>> Konstantin, if this turns out to be affecting a lot of people, do you >>> think we could get an errata notice for this? >> >> I would not strongly object against EN, but this is underqualified >> bug for the releng branch, IMO. The issue does not affect the system >> integrity, since the looping process must be killable. >> >> If secteam agrees to spent the time on this, why not ? But IMO it inflates >> the meaning of the releng branch. For the 'new suport model', this >> would have clean resolution, but for 10.x I am not sure what to do. > > The definition of "errata" was always largely based on whether there was > a significant impact to users, which is why I was asking if anyone else > was seeing this problem -- if I'm the only person, it definitely doesn't > deserve an EN, but if *everybody* using Chrome is running into this I think > it might make sense even though the impact on any one user is only at the > level of annoyance. > > Nobody else seems to be chiming in to say that they're affected by this > bug yet though... > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGo8CXFE-Kxpgh7hL1c0DrzZ6L6B8ZNE_rC0_CHp97PGx33BQ>