04-20-2021, 12:21 AM
(This post was last modified: 04-20-2021, 12:23 AM by TheOldPresbyope.
Edit Reason: ETA
)
@bgonc
I am using a USB DAC on my DSI touchscreen-equipped testbox and I haven't seen any memory usage problem with hours of testing on an unmodified moOde 7.1.0 installation.
I restarted chromium-browser with the --single-process option and it also has been running for hours now without any memory usage problem. Actually the memory usage dropped some 60MB because of the fewer number of subprocesses (this is mentioned in the design docs). There are some interesting anomalies. For example, 3 zygote subprocesses are running, just as before.
At this point, I suppose I'd say this is may be a viable band-aid solution for those who experience the problem but I won't feel comfortable until I know the root cause. The chromium dev design docs say of this option
Since the OOM condition results in catatonia for us, their architectural caveat may be moot but the "may contain bugs" remark is sobering.
I just noticed your system includes an I2S HiFiBerry DAC+ as does @Alaini93's. Several other contributors to this issue are using I2S HiFiBerry AMP2. I thought we'd shown the coincidence likely was a red herring up-thread but curiously it keeps recurring. I think I have a DAC+ around somewhere but I have no easy way of inserting it into the system containing my touchscreen.
Starting HDMI test later.
Regards,
Kent
ETA - but I just saw @Alaini93 's follow-up post so maybe not such a good band-aid solution after all.
I am using a USB DAC on my DSI touchscreen-equipped testbox and I haven't seen any memory usage problem with hours of testing on an unmodified moOde 7.1.0 installation.
I restarted chromium-browser with the --single-process option and it also has been running for hours now without any memory usage problem. Actually the memory usage dropped some 60MB because of the fewer number of subprocesses (this is mentioned in the design docs). There are some interesting anomalies. For example, 3 zygote subprocesses are running, just as before.
At this point, I suppose I'd say this is may be a viable band-aid solution for those who experience the problem but I won't feel comfortable until I know the root cause. The chromium dev design docs say of this option
Quote:The single process model provides a baseline for measuring any overhead that the multi-process architectures impose. It is not a safe or robust architecture, as any renderer crash will cause the loss of the entire browser process. It is designed for testing and development purposes, and it may contain bugs that are not present in the other architectures.
Since the OOM condition results in catatonia for us, their architectural caveat may be moot but the "may contain bugs" remark is sobering.
I just noticed your system includes an I2S HiFiBerry DAC+ as does @Alaini93's. Several other contributors to this issue are using I2S HiFiBerry AMP2. I thought we'd shown the coincidence likely was a red herring up-thread but curiously it keeps recurring. I think I have a DAC+ around somewhere but I have no easy way of inserting it into the system containing my touchscreen.
Starting HDMI test later.
Regards,
Kent
ETA - but I just saw @Alaini93 's follow-up post so maybe not such a good band-aid solution after all.
