#1006148 Chromium constantly tries to access CPUFreq API in VMs

Package:
chromium
Source:
chromium
Description:
web browser
Submitter:
MichaIng
Date:
2022-02-19 22:57:03 UTC
Severity:
normal
#1006148#5
Date:
2022-02-19 20:51:22 UTC
From:
To:
Hey guys,

I recognised that Chromium on Bullseye is constantly trying to access
the CPUFreq API, even when it runs within a VM where this API is
expected to be not available. This triggers constant error messages:
-------
*** stack smashing detected ***: terminated
[0219/213510.894782:ERROR:file_io_posix.cc(144)] open
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or
directory (2)
[0219/213510.895538:ERROR:file_io_posix.cc(144)] open
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or
directory (2)
*** stack smashing detected ***: terminated
[0219/213511.092091:ERROR:file_io_posix.cc(144)] open
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or
directory (2)
[0219/213511.093493:ERROR:file_io_posix.cc(144)] open
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or
directory (2)
-------

This does not happen on Bookworm, so likely it got fixed upstream in the
meantime? Probably this fix can be cherry picked for Debian Bullseye?

Best regards,

Micha
#1006148#8
Date:
2022-02-19 22:43:42 UTC
From:
To:
On Sat, 19 Feb 2022 21:51:22 +0100 MichaIng wrote:
 > Package: chromium
 > Version: 90.0.4430.212-1

 >


Hi, please make sure that you're running security updates for bullseye.
Chromium 98.0.4758.102-1~deb11u1 is in stable-security and
stable-proposed-updates. Chromium 90 is full of security holes and
should not be used.
#1006148#13
Date:
2022-02-19 22:54:42 UTC
From:
To:
Ah sorry, my bad, the errors do show up on version 98.0.4758.102-1~deb11u1.

So then it is not an upstream issue but a difference between the build
or environment on Bullseye vs Bookworm.

Best regards,

Micha