Bug#1006148: Chromium constantly tries to access CPUFreq API in VMs

[MichaIng]

Package: chromium
Version: 90.0.4430.212-1

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

[MichaIng]

Package: chromium
Version: 98.0.4758.102-1~deb11u1

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