From owner-freebsd-chromium@freebsd.org Mon Jul 6 21:42:02 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9195D99531E for ; Mon, 6 Jul 2015 21:42:02 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7C1E21C63 for ; Mon, 6 Jul 2015 21:42:02 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7ABFB99531D; Mon, 6 Jul 2015 21:42:02 +0000 (UTC) Delivered-To: chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A5E999531C for ; Mon, 6 Jul 2015 21:42:02 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 507C81C61 for ; Mon, 6 Jul 2015 21:41:59 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id t66Lc3RB062103 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 6 Jul 2015 14:38:04 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be yuri.doctorlan.com Message-ID: <559AF53A.2040207@rawbw.com> Date: Mon, 06 Jul 2015 14:38:02 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: chromium@FreeBSD.ORG Subject: Crash when right mouse button click on download file Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jul 2015 21:42:02 -0000 Crash is on 10.1 when some file is being downloaded (download tab in the bottom with progress indicator). Right mouse button click=SEGV. 43.0.2357.130 (64-bit) Yuri From owner-freebsd-chromium@freebsd.org Tue Jul 7 17:47:05 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C30C4AD28 for ; Tue, 7 Jul 2015 17:47:05 +0000 (UTC) (envelope-from koljasha@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A34F5111B for ; Tue, 7 Jul 2015 17:47:05 +0000 (UTC) (envelope-from koljasha@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9FB83AD27; Tue, 7 Jul 2015 17:47:05 +0000 (UTC) Delivered-To: chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8553AAD25 for ; Tue, 7 Jul 2015 17:47:05 +0000 (UTC) (envelope-from koljasha@gmail.com) Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BD861104 for ; Tue, 7 Jul 2015 17:47:05 +0000 (UTC) (envelope-from koljasha@gmail.com) Received: by ykdr198 with SMTP id r198so184542305ykd.3 for ; Tue, 07 Jul 2015 10:47:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=eMmLOW0vaTHaURDc0HT6avHs/2jQf3+n5220KLPLBI4=; b=DdOOnQD3UalDVUsCZTmWqRsJa8c7t3/p59C+EwBMq2POuWOA3O08WRg2nDS6kDj0CD jB/YbvbAjQW0/dcLJCBmNYtawea3gjB0OAXf+RePz/WrKlYPE5h6M65pv6/WEoUFZTWt IwmhGz6wvk0MGD3zPIg76RAxCbt1BQBfbRaQMwCpNeKq0WOY0L4X3dRNRwvq591SC6fg Z3mUa+XHwgwmM4Cp4V2/qfK1zqaVkHD7q1mwbdk3air3Za38tloCCv2JFpfzte2KTlan yuyU88aO5wdaPTTHFrV0Egg9epGSti/CP7cSkRZvgXs+YjyOQ4wzmv1s/pMPCGaUjmgy 0Wjw== MIME-Version: 1.0 X-Received: by 10.170.194.19 with SMTP id l19mr6011882yke.99.1436291224411; Tue, 07 Jul 2015 10:47:04 -0700 (PDT) Received: by 10.37.105.67 with HTTP; Tue, 7 Jul 2015 10:47:04 -0700 (PDT) Date: Tue, 7 Jul 2015 20:47:04 +0300 Message-ID: Subject: About Chromium From: =?UTF-8?B?0J3QuNC60L7Qu9Cw0Lkg0KTQtdC00L7RgNC+0LI=?= To: chromium@FreeBSD.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2015 17:47:06 -0000 Hello. I apologize for my English, I use a translator. I have a few problems, when I use Chromium. I use PC-BSD and noticed a few problems using the browser. Initially, the version 42 I collected from the ports, now I use 43 form packets (well, for a long time to collect ((( ). And that's what the problems: The first, version of Chromium 42 and 43 crashed (I use 43.0.2357.130 now, whether before, I do not know) when I downloading a file, or after downloading files and I click on the small arrow that lets you open the folder with the downloaded file, or for example to cancel download. If I just have to click on the downloaded file, then all is well. Chromium crashed by clicking on the arrow. Second, version of Chromium 43.0.2357.125 crashed, if I go to Settings - version 43.0.2357.130 - this problem is solved. Third, I noticed that in the version 43.0.2357.130 (whether problem before - I do not know) if I go to Settings, then the processor is loaded at 50-70% (normal operation up to 25%), while if even I close Chromium, it remains Chrom is a process that the executive CPU by 50-70%. This process is only closed if I to kill him by hand. An opportunity like something you can solve these problems, they are not critical, but it is unpleasant. Thanks. From owner-freebsd-chromium@freebsd.org Sat Jul 11 03:37:32 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7415E996D3B for ; Sat, 11 Jul 2015 03:37:32 +0000 (UTC) (envelope-from bounces+73574-e33c-freebsd-chromium=freebsd.org@sendgrid.net) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3777381B for ; Sat, 11 Jul 2015 03:37:31 +0000 (UTC) (envelope-from bounces+73574-e33c-freebsd-chromium=freebsd.org@sendgrid.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=FWOq7dzng4Ne/7yTPpCCEB4dOJg=; b=h067rNpCV8L7tnHL+6 oit0h3N5LJyceFUGngEu5HXUvZq/WgxVxCzc42nDAu5Oe1/khZTAeHo+nmY+RnUI RPO9iH8GabrQy5rU+2y68D4P6pIH9/vftN5HuSCWZUOC/O8fp9GyTcI9sVf8NP14 D/kVK6BSpktYNzEQutAEvApZ8= Received: by filter0588p1mdw1.sendgrid.net with SMTP id filter0588p1mdw1.24791.55A08F4E16 2015-07-11 03:36:51.586185153 +0000 UTC Received: from mail.tarsnap.com (ec2-54-86-246-204.compute-1.amazonaws.com [54.86.246.204]) by ismtpd-032 (SG) with ESMTP id 14e7b2fddd5.136.3a359 for ; Sat, 11 Jul 2015 03:36:51 +0000 (UTC) Received: (qmail 43105 invoked from network); 11 Jul 2015 03:33:07 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 11 Jul 2015 03:33:07 -0000 Received: (qmail 9313 invoked from network); 11 Jul 2015 03:35:52 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 11 Jul 2015 03:35:52 -0000 Message-ID: <55A08F18.7060803@freebsd.org> Date: Fri, 10 Jul 2015 20:35:52 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Konstantin Belousov , freebsd-chromium@freebsd.org Subject: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] References: <201410051736.s95Ha0U7010634@svn.freebsd.org> In-Reply-To: <201410051736.s95Ha0U7010634@svn.freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SG-EID: XhyBwObMhraAR+zdwMupjVGEs/UG/hkvmklqQBd8XaaHnRZel/ukO99ClrfA/k7X/WWf/BOcvqgowX img42ucLTUKFWbnIGvbFLEtpTwPmD02GOGYUmjgDPyszBw673pcVq/Pq+SjjrtjXhrEmXZ54uFknk9 rZzUN6wvEeJwjg9v+rRlLg7uD8aMtwS8l6z/ X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 03:37:32 -0000 The bug fixed by this commit is causing chrome processes to get stuck spinning at 100% CPU on my FreeBSD 10.1-RELEASE laptop -- chrome is trying to read the kern.proc.pid.# sysctl (I think in order to get the status of a crashed rendering process) and it's going into an infinite ERESTART loop. 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? Colin Percival On 10/05/14 10:36, Konstantin Belousov wrote: > Author: kib > Date: Sun Oct 5 17:35:59 2014 > New Revision: 272566 > URL: https://svnweb.freebsd.org/changeset/base/272566 > > Log: > On error, sbuf_bcat() returns -1. Some callers returned this -1 to > the upper layers, which interpret it as errno value, which happens to > be ERESTART. The result was spurious restarts of the sysctls in loop, > e.g. kern.proc.proc, instead of returning ENOMEM to caller. > > Convert -1 from sbuf_bcat() to ENOMEM, when returning to the callers > expecting errno. > > In collaboration with: pho > Sponsored by: The FreeBSD Foundation (kib) > MFC after: 1 week > > Modified: > head/sys/kern/kern_descrip.c > head/sys/kern/kern_proc.c > > Modified: head/sys/kern/kern_descrip.c > ============================================================================== > --- head/sys/kern/kern_descrip.c Sun Oct 5 11:16:16 2014 (r272565) > +++ head/sys/kern/kern_descrip.c Sun Oct 5 17:35:59 2014 (r272566) > @@ -3097,7 +3097,7 @@ export_kinfo_to_sb(struct export_fd_buf > } > efbuf->remainder -= kif->kf_structsize; > } > - return (sbuf_bcat(efbuf->sb, kif, kif->kf_structsize)); > + return (sbuf_bcat(efbuf->sb, kif, kif->kf_structsize) == 0 ? 0 : ENOMEM); > } > > static int > > Modified: head/sys/kern/kern_proc.c > ============================================================================== > --- head/sys/kern/kern_proc.c Sun Oct 5 11:16:16 2014 (r272565) > +++ head/sys/kern/kern_proc.c Sun Oct 5 17:35:59 2014 (r272566) > @@ -1208,21 +1208,25 @@ kern_proc_out(struct proc *p, struct sbu > #ifdef COMPAT_FREEBSD32 > if ((flags & KERN_PROC_MASK32) != 0) { > freebsd32_kinfo_proc_out(&ki, &ki32); > - error = sbuf_bcat(sb, &ki32, sizeof(ki32)); > + if (sbuf_bcat(sb, &ki32, sizeof(ki32)) != 0) > + error = ENOMEM; > } else > #endif > - error = sbuf_bcat(sb, &ki, sizeof(ki)); > + if (sbuf_bcat(sb, &ki, sizeof(ki)) != 0) > + error = ENOMEM; > } else { > FOREACH_THREAD_IN_PROC(p, td) { > fill_kinfo_thread(td, &ki, 1); > #ifdef COMPAT_FREEBSD32 > if ((flags & KERN_PROC_MASK32) != 0) { > freebsd32_kinfo_proc_out(&ki, &ki32); > - error = sbuf_bcat(sb, &ki32, sizeof(ki32)); > + if (sbuf_bcat(sb, &ki32, sizeof(ki32)) != 0) > + error = ENOMEM; > } else > #endif > - error = sbuf_bcat(sb, &ki, sizeof(ki)); > - if (error) > + if (sbuf_bcat(sb, &ki, sizeof(ki)) != 0) > + error = ENOMEM; > + if (error != 0) > break; > } > } > @@ -1777,7 +1781,8 @@ proc_getauxv(struct thread *td, struct p > else > #endif > size = vsize * sizeof(Elf_Auxinfo); > - error = sbuf_bcat(sb, auxv, size); > + if (sbuf_bcat(sb, auxv, size) != 0) > + error = ENOMEM; > free(auxv, M_TEMP); > } > return (error); > @@ -2363,9 +2368,10 @@ kern_proc_vmmap_out(struct proc *p, stru > strlen(kve->kve_path) + 1; > kve->kve_structsize = roundup(kve->kve_structsize, > sizeof(uint64_t)); > - error = sbuf_bcat(sb, kve, kve->kve_structsize); > + if (sbuf_bcat(sb, kve, kve->kve_structsize) != 0) > + error = ENOMEM; > vm_map_lock_read(map); > - if (error) > + if (error != 0) > break; > if (last_timestamp != map->timestamp) { > vm_map_lookup_entry(map, addr - 1, &tmp_entry); > > > -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-chromium@freebsd.org Sat Jul 11 11:27:00 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67E819986BB for ; Sat, 11 Jul 2015 11:27:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3C561DE6; Sat, 11 Jul 2015 11:26:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t6BBQsLn019093 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 11 Jul 2015 14:26:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t6BBQsLn019093 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t6BBQs4h019088; Sat, 11 Jul 2015 14:26:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 11 Jul 2015 14:26:54 +0300 From: Konstantin Belousov To: Colin Percival Cc: freebsd-chromium@freebsd.org Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] Message-ID: <20150711112654.GC2080@kib.kiev.ua> References: <201410051736.s95Ha0U7010634@svn.freebsd.org> <55A08F18.7060803@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55A08F18.7060803@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 11:27:00 -0000 On Fri, Jul 10, 2015 at 08:35:52PM -0700, Colin Percival wrote: > The bug fixed by this commit is causing chrome processes to get stuck > spinning at 100% CPU on my FreeBSD 10.1-RELEASE laptop -- chrome is > trying to read the kern.proc.pid.# sysctl (I think in order to get the > status of a crashed rendering process) and it's going into an infinite > ERESTART loop. > > 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. From owner-freebsd-chromium@freebsd.org Sat Jul 11 20:39:07 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E97739970DA for ; Sat, 11 Jul 2015 20:39:07 +0000 (UTC) (envelope-from bounces+73574-e33c-freebsd-chromium=freebsd.org@sendgrid.net) Received: from o1.l99.sendgrid.net (o1.l99.sendgrid.net [198.37.153.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C47EB4 for ; Sat, 11 Jul 2015 20:39:07 +0000 (UTC) (envelope-from bounces+73574-e33c-freebsd-chromium=freebsd.org@sendgrid.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=Tl2VNp3WGzJ27ZP7RJZAhuetWBQ=; b=wcK+wk82oFE5/EFYfV EXM+CZxEdPFy0EO8A7vNO6kE4tBBuMc1uypr+fgk3I1WliFrssB+b7VMsh6s38j9 C/sSslJphdplnJ+qe7MJdj36NuPB7WXjoo7BbdVU0N7GMJWXtLRqZLiNrj3anFSW 7H8g0Victa+gQE1pk4L1I7sCM= Received: by filter0487p1mdw1.sendgrid.net with SMTP id filter0487p1mdw1.30193.55A17EE96 2015-07-11 20:39:05.27441479 +0000 UTC Received: from mail.tarsnap.com (ec2-54-86-246-204.compute-1.amazonaws.com [54.86.246.204]) by ismtpd-015 (SG) with ESMTP id 14e7ed7beb1.17f0.68318 for ; Sat, 11 Jul 2015 20:39:05 +0000 (UTC) Received: (qmail 75358 invoked from network); 11 Jul 2015 20:35:21 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 11 Jul 2015 20:35:21 -0000 Received: (qmail 63663 invoked from network); 11 Jul 2015 20:38:04 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 11 Jul 2015 20:38:04 -0000 Message-ID: <55A17EAC.1000604@freebsd.org> Date: Sat, 11 Jul 2015 13:38:04 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Konstantin Belousov CC: freebsd-chromium@freebsd.org Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] References: <201410051736.s95Ha0U7010634@svn.freebsd.org> <55A08F18.7060803@freebsd.org> <20150711112654.GC2080@kib.kiev.ua> In-Reply-To: <20150711112654.GC2080@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SG-EID: XhyBwObMhraAR+zdwMupjVGEs/UG/hkvmklqQBd8XaaHnRZel/ukO99ClrfA/k7XDdn+uCrw6wRbrz ONP40jVmFbe2gEbiksL5l1zf0OrYJMfwmwtRyn+Djx51houewYfviAu9/t6sr1N8gYrQItIH5UxDb7 sioXe6W3aR/0oEKYj0PTB09hSEhVhgd/XowU X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 20:39:08 -0000 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 From owner-freebsd-chromium@freebsd.org Sat Jul 11 20:58:22 2015 Return-Path: Delivered-To: freebsd-chromium@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72CB3997501 for ; Sat, 11 Jul 2015 20:58:22 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FC35A57; Sat, 11 Jul 2015 20:58:22 +0000 (UTC) (envelope-from miguelmclara@gmail.com) Received: by igcqs7 with SMTP id qs7so34133834igc.0; Sat, 11 Jul 2015 13:58:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KEv0Vwt4O3Ve2cKF+czGP/IA19k8n0hPj3dcNKv33Us=; b=xRZ2UPEgJXGW5j8HDOfALZWrPyzVIIE4hNFOtMuz3dYKycVtanOdX+d2ROQtDmTj+h Dgb9/gLLFbeIdyTuS7liLBe3nS/jsaZok3T1c2g+OKGpLvzfOYWp5eYMg/qsF81Qwl+7 eQ3oaNMt3vIipV5q0nTr0lWwfAHWdkrayOWXZsjfGOdsgovClpG/h4Gy/L7W8oCBQqQ8 bnS3BtHaWAP3mh5f/GUrJVTj9sp0T328eSH4rI7ZuLcGaYZXmTbj6MgrGy1lLDV4pj/Q HkpYP4CFI5N2u9GTy1rFZ3JdMyefyZiXgL5PO+YaNvAgkHfWDocuLiOeMYrY7YfQph3n m3+w== X-Received: by 10.50.143.101 with SMTP id sd5mr5277726igb.44.1436648301689; Sat, 11 Jul 2015 13:58:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.240.146 with HTTP; Sat, 11 Jul 2015 13:57:42 -0700 (PDT) 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> From: Miguel C Date: Sat, 11 Jul 2015 21:57:42 +0100 Message-ID: Subject: Re: chrome processes stuck at 100% cpu [Re: svn commit: r272566 - head/sys/kern] To: Colin Percival Cc: Konstantin Belousov , chromium-list freebsd Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jul 2015 20:58:22 -0000 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 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"