04-19-2021, 12:55 PM
Hi
first time contributor to the forum, loving Moode since early 2020 .
I have a raspberry Pi 3B with an Hifiberry DAC + Pro and an Osoyoo 3.5" DSI touch screen and with Moode 7.1.0 installed
I verified a similar problem with Chromium memory usage increasing until freezing Moode completely. This started to happen since, at least, version 7.0.1 (although looking retrospectively I had previously several Chromium Aw! Snap Windows the could be from a similar problem). The problem occurs typically around 27 minutes after pausing the music player.
Trying to avoid being a "Me too!" I used the Local UI display with HDMI on , and with HDMI off while using the DSI display . Independently of the HDMI it always resulted in the system becoming completely frozen after some time.
Although not proficient in Linux , I think I found a work around to prevent the problem to occur. I edited the file .xinitrc and added at the end of the chromium-browser launch line:
--single-process --no-zygote --no-sandbox
It is now paused for more than 1 hour without any signs of increase in memory usage (with htop showing memory usage to vary between 236 and 259 Mb).
PS: I do not know why it works but I realized using top that the Chromium process that was using the memory had a "type=zygote" and tried to follow from there.
first time contributor to the forum, loving Moode since early 2020 .
I have a raspberry Pi 3B with an Hifiberry DAC + Pro and an Osoyoo 3.5" DSI touch screen and with Moode 7.1.0 installed
I verified a similar problem with Chromium memory usage increasing until freezing Moode completely. This started to happen since, at least, version 7.0.1 (although looking retrospectively I had previously several Chromium Aw! Snap Windows the could be from a similar problem). The problem occurs typically around 27 minutes after pausing the music player.
Trying to avoid being a "Me too!" I used the Local UI display with HDMI on , and with HDMI off while using the DSI display . Independently of the HDMI it always resulted in the system becoming completely frozen after some time.
Although not proficient in Linux , I think I found a work around to prevent the problem to occur. I edited the file .xinitrc and added at the end of the chromium-browser launch line:
--single-process --no-zygote --no-sandbox
It is now paused for more than 1 hour without any signs of increase in memory usage (with htop showing memory usage to vary between 236 and 259 Mb).
PS: I do not know why it works but I realized using top that the Chromium process that was using the memory had a "type=zygote" and tried to follow from there.
