From owner-freebsd-ports-bugs@freebsd.org Wed Sep 25 08:09:46 2019 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E9293FEA19 for ; Wed, 25 Sep 2019 08:09:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 46dW1k5z9jz4XrT for ; Wed, 25 Sep 2019 08:09:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CC7AEFEA15; Wed, 25 Sep 2019 08:09:46 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9F21FEA14 for ; Wed, 25 Sep 2019 08:09:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46dW1k52Fsz4XrP for ; Wed, 25 Sep 2019 08:09:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 891B8CC71 for ; Wed, 25 Sep 2019 08:09:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x8P89kvU098280 for ; Wed, 25 Sep 2019 08:09:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8P89k8s098279 for ports-bugs@FreeBSD.org; Wed, 25 Sep 2019 08:09:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 240806] www/chromium: Newly Installed via pkg upgrade Causes chromium to run at near 100% All CPU Cores Overheating Causing CPU Thermal Shutdown Date: Wed, 25 Sep 2019 08:09:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jlmales@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Sep 2019 08:09:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D240806 Bug ID: 240806 Summary: www/chromium: Newly Installed via pkg upgrade Causes chromium to run at near 100% All CPU Cores Overheating Causing CPU Thermal Shutdown Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: jlmales@gmail.com Flags: maintainer-feedback?(chromium@FreeBSD.org) Assignee: chromium@FreeBSD.org Created attachment 207787 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D207787&action= =3Dedit Console from last boot and showing some of the excessive CPU Core use of Chromium vs Firefox After doing a pkg update 20190925 02:19+0000 UTC that performed many XFCE updates that seemed related to "Installed packages to be UPGRADED:" xfce: 4.12_1 -> 4.14 based set of updates there was "New packages to be INSTALLED= :" xfce4-screensaver: 0.1.8. The pkg upgrade proceed with no issues and the FreeBSD 11.3 based system was immediately rebooted by me not only due to the extent of the many upgraded XFCE4 packages, but there was an update for xorg-server: 1.18.4_11,1 -> 1.18.4_12,1. The reboot and CLI startx (to start xfce4 by default) proceeded just fine, = and clearly a new look an feel for XFCE4. I was away from the machine for abou= t 8 miinutes and upon return found the laptop powered off. There was no power interruption and the laptop battery is in excellent condition and 100% chan= ged. Restarted the laptop where many FreeBSD 11.3 kernel messages occurred that looked like VFS dumping. The messages occurred to fast and my phone SD car= d is not working so unable to to take pics or video of issues. The FreeBSD kern= el then immediately rebooted. Started XFCE4 as usual via CLI after reboot via startx. I am still new to FreeBSD, but have used Unix since 1999 as only OS. I have used Unix prior on/off as result of my career and even when in high school.= I do not know if the boot messages are stored in some place I can still retri= eve the boot messages that may shed some light on this matter. Started chromium and widget displayed saying chromium configuration file is corrupted. Yet chromium able to restart all windows and tabs previously op= en.=20=20 Started to key in bug report at time not aware of real cause of issue, but = some other cause such as XFCE. As entering new bug report system shut down with = no warning. Discovered laptop bottom very very warm. Suspect this and prior shutdown due to system overheating. System has never overheated in past. Allowed system to cool down as was very hot underneath most of laptop area. Rebooted. Something let me to check CPU temperatures and foudn all cores running near 80+% and all CPU cores about 82+C. Checked htop and sense from htop was chromium was cause of all cores use and resulting very high all CPU core temperatures. Killed chromium and as soon as did all CPU cores dropped to = near Zero usage. There was a small immediate drop in all CPU core temperatures.= It took a while for all CPU core temperatures to drop to reasonable temperatur= es due to level and time CPU cores where running over 80%. During that time r= an CLI commands to take CPU core temperatures. Started chromium again and as soon as did all cores of CPU went to over 80%= and all CPU cores temperatures started to rise quickly. Again tool CPU core temperatures via CLI. Then killed chromium again and again all CPU cores dropped to near Zero and all CPU cores started to drop in temperature again. I had been running chromium for few weeks prior to the pkg update of 201909= 25 02:19 that involved in summary xfce: 4.12_1 -> 4.14 and xorg-server: 1.18.4_11,1 -> 1.18.4_12,1. Both sets of updates likely, but not certain = may have some impact on chromium causing CPU cores to all run 80+% and causing thermal CPU shutdown and file/system corruption. I would thing others would be also impacted by this issue at least from excessive CPU core use that may also lead to other systems having a CPU the= rmal protection shut down. Started firefox and other than basic normal all cores high use for about 20 seconds system CPU core temperatures are running in the expected normal ran= ge of 68C-70C. Therefore this bug was entered via firefox as chromium would have caused CPU cores to overheat and shut down system before able to complete this bug rep= ort. Also note chromium was running after the pkg upgrade/reboot that lead to the first in hindsight CPU thermal shutdown. --=20 You are receiving this mail because: You are the assignee for the bug.=