Local display function fails with HDMI in moOde 7.0.1

[Tim Curtis]

I encountered this issue on a fresh moode 7.1.0 install.
My hardware is a Pi 3B+ with official 7" DSI touchscreen and HiFi berry AMP2.
In addition to the sudden memory usage increase of chromium after some time I noticed the CPU usage to be significantly higher all the time compared to 6.7.1.
I'm seeing ~18% on 6.7.1 vs ~ 79% on 7.1.0 (just after booting and stays at this level for minutes).

Moreover I installed different browsers and updated chromium on 7.1.0 - didn't make a difference, at least considering the high CPU usage. With different browsers (Firefox, Vivaldi, Midori) the UI is very unresponsive right from the beginning and CPU load is even higher (ranging from 90% to well above 130%), so I didn't check about memory usage spiking.
As last test I updated the whole Raspi OS via apt update && apt upgrade to 10.9 - also didn't make a difference.

So has anybody else made progress investigating this?
For now I restored my backup of 6.7.1.

Quick test and below is what I see wrt CPU on my end. It's a 3B with no HAT and a 7" Pi Touch. I'm not seeing any unusual CPU utilization.

It's not obvious to me what might be happening on your end.

Idle

Code:

CPU: 1.2 GHz | LOAD: 7% | TEMP: 46°C | RAM_USED: 34% | DISK_USED: 79% | DISK_FREE: 802M | FPM_POOL: 10 workers  
CPU: 1.2 GHz | LOAD: 4% | TEMP: 45°C | RAM_USED: 34% | DISK_USED: 79% | DISK_FREE: 802M | FPM_POOL: 10 workers  
CPU: 1.2 GHz | LOAD: 9% | TEMP: 45°C | RAM_USED: 34% | DISK_USED: 79% | DISK_FREE: 802M | FPM_POOL: 10 workers  

Playing radio station

Code:

CPU: 1.2 GHz | LOAD: 45% | TEMP: 48°C | RAM_USED: 34% | DISK_USED: 79% | DISK_FREE: 802M | FPM_POOL: 10 workers
CPU: 1.2 GHz | LOAD: 49% | TEMP: 48°C | RAM_USED: 35% | DISK_USED: 79% | DISK_FREE: 802M | FPM_POOL: 10 workers
CPU: 1.2 GHz | LOAD: 47% | TEMP: 49°C | RAM_USED: 34% | DISK_USED: 79% | DISK_FREE: 802M | FPM_POOL: 10 workers

The suspected issue in chromium-browser that apparently causes memory to leak over time or one of the threads to crash or some combo of bad things is something that the chromium project is responsible for investigating and fixing. I think this is the project site https://www.chromium.org/Home