screen frozen sometimes, server keeps running

[Eli]

@sdetweil
The -m would just recalc to MByte instead of bytes, or?

I agree, the shots still show some free memory - but as mentioned: it fills up (free ‘frei’) size is decreasing nearly continuously, sometimes increasing.
I don’t know why. If it would float around one value I would say this is due to the picture size loaded, but it starts with a lot of free mem and then comes down to low numbers.

As only the mirror is running on this device, then only variation in display is the pictures.
And from time to time an update on wheather or calendar, but that should not eat memory, I would think.

I might try to increase the picture update rate to 1h or so - so that only a few pictures get loaded. Then it might be better…I also need to try disabling the background image and see if it still freezes.

Would you agree that just showing static content should keep the memory resources stable?

About swap: yes, I activated overlay file system to not store on sd card.

[sdetweil]

@Eli it will fluctuate… only time I see freeze is when I run out of memory AND swap…

[Eli]

@sdetweil Well, yes. But Swap is disabled as I enabled the overlay file system in raspi-config, so only RAM is used, I would assume.

I tested to reduce the amount of pictures shown in MMM-BackgroundSlideshow. When I display a new picture each 10 mins, the issue doe snot occure (before it was every 30s).

So, that definitely helps to mitigate the issue. The question still is, if this is cause by some bug in the module or generally in the mirror due to low RAM.

[sdetweil]

@Eli I don’t know. I haven’t seen any reports of problem w this module, and looking through the code, it seems it minimizes photo memory.

the actual memory is consumed in the browser, so there could be problems there

[Eli]

@sdetweil
Thanks for checking! Really appreciate that.

I could reduce timing even more, still working fine for me.

Perhaps the RAM cleaning process is too slow to load new picture every 30s. I also think it is more a browser/system issue than the module itself.

For me that is sufficient, so closed.