Heavy CPU use with HDMI LocalUI, normal?

[pfeuffer]

What version of chromium-browser?

104.0.5112.105-rpt2  I'm not sure what the prior version was, but it gave the same behavior.

[Tim Curtis]

What version of chromium-browser?

104.0.5112.105-rpt2  I'm not sure what the prior version was, but it gave the same behavior.

Thats the same version on my systems. One of them is connected to an HDMI display and it's usually on during the day and evening so like >12 hours. I've never experienced any CPU or memory issues.

Note there was a memory leak issue in the versions of chromium-browser used in moOde prior to release 8.1.0 but it took something like 3 hours to manifest itself. The leak went away in chromium-browser 101.0.4951.57-rpt2 which we shipped in release 8.1.0.

Here's some command output from that system mentioned above.

Code:

pi@kef:~ $ moodeutl -m
CPU: 1.4 GHz, LOAD: 6% 60C | MEM: 40% used | DISK: 9% used, 26G free | PHP: 9 workers

pi@kef:~ $ free -h
              total        used        free      shared  buff/cache   available
Mem:           909Mi       268Mi       105Mi        27Mi       535Mi       556Mi
Swap:             0B          0B          0B

pi@kef:~ $ moodeutl -s
Gathering info...

S Y S T E M   P A R A M E T E R S

moOde release           = 8.2.2 2022-MM-DD
RaspiOS                 = 11.5
Linux kernel            = 5.15.61-v8+ #1579
Platform                = Pi-3B+ 1.3 1GB
Architecture            = aarch64 (64-bit)
System uptime           = up 10 hours, 48 minutes
Timezone                = America/Detroit
Current time            = 2022-10-18 18:20:16
.
.
.
L O C A L   D I S P L A Y   S E T T I N G S

Local UI display        = On
Mouse cursor            = Off
Screen blank            = 600 Secs
Wake display on play    = On
Brightness              = 255
Pixel aspect ratio      = Default
Rotate screen           = 0 Deg

I also recently tested a system with an attached Pi 7" Touch display and no issues after >4 hours.

I'm not sure what might be happening in your particular case but maybe check the usual suspects.

- Is there any other 3rd party software in the mix or custom modifications/tweaks?
- Was apt upgrade or dist-upgrade run?
- Is SDCard known to be solid?
- Does the issue occur when system is idle or when its playing?


-Tim