01-01-2023, 11:08 PM
@chinaski33
I'm not sure why you fell back to moOde 8.0.0. As Tim said earlier, we were having problems with the Chromium browser and its memory leakage before 8.1.x so I wouldn't expect success.
Keep in mind that the moOde build simply incorporates whatever Chromium browser packages are available in the official raspberry pi and debian repositories. At some point, as the package versions advanced, the memory leakage problem abated, but it wasn't due to anything we did. As an aside, reading the Chromium developer forum is not very informative for us outsiders.
As for the screen blanking, sorry, I don't believe that this should have an effect on this issue, I was just curious about the local display settings you've chosen.
I've been running moOde 8.2.4 on an RPi3B+ and 7-inch display for some hours now. Like Tim, I'm not seeing memory usage increasing and the screen response was quick when I checked just now. This is quite unlike the behavior I was seeing when this problem was first being explored some years ago. Then the browser ultimately would consume all memory and freeze the system.
Regards,
Kent
I'm not sure why you fell back to moOde 8.0.0. As Tim said earlier, we were having problems with the Chromium browser and its memory leakage before 8.1.x so I wouldn't expect success.
Keep in mind that the moOde build simply incorporates whatever Chromium browser packages are available in the official raspberry pi and debian repositories. At some point, as the package versions advanced, the memory leakage problem abated, but it wasn't due to anything we did. As an aside, reading the Chromium developer forum is not very informative for us outsiders.
As for the screen blanking, sorry, I don't believe that this should have an effect on this issue, I was just curious about the local display settings you've chosen.
I've been running moOde 8.2.4 on an RPi3B+ and 7-inch display for some hours now. Like Tim, I'm not seeing memory usage increasing and the screen response was quick when I checked just now. This is quite unlike the behavior I was seeing when this problem was first being explored some years ago. Then the browser ultimately would consume all memory and freeze the system.
Regards,
Kent
