Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Sep 2019 08:09:45 +0000
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
Message-ID:  <bug-240806-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-240806-7788>