08-01-2021, 01:03 PM
(07-31-2021, 04:19 PM)gforster Wrote:Maybe moOde could just switch to Firefox and be done with it, if Chromium is going to use up all the memory for no good reason.(07-31-2021, 03:54 PM)jv275475 Wrote:(07-30-2021, 12:01 PM)gforster Wrote:(07-29-2021, 06:03 PM)jv275475 Wrote:(07-29-2021, 04:43 PM)Sehnsucht Wrote: Is chromium there as part of your touchscreen solution? Perhaps try a different browser? Uninstall chromium. Or try using another mpd client temporarily and see if it reoccurs. (I don't use the officlal moOde web interface at all - it's nice but i'm not interested in playlists and album art and radio stations etc, so having configured moOde using the web interface I use an android app to select music to play). Maybe stay connected to the pi via SSH whatever diagnosis you try, then run htop and see if the memory increase happens slowly over time or something triggers it. If it's chromium, kill it via htop or kill instead of rebooting - is that a 100% fix? Anything interesting in the log files in /var/log at the point you have problems?
Thanks for the suggestions. Chromium is part of the Local UI display of MoOde, I use MoOde through the touchscreen. The reason for this setup is I want to have all my music with good sound quality at work. I cannot anything into my company's network, so I use a Pi with MoOde with the touchscreen + USB disk and DAC. All standalone, no network connection.
I've seen suggestions to replace Chromium with Firefox, but I'd rather avoid big modifications to MoOde. I'd rather stay on 6.7.1 in that case.
I did the modification and replaced Chromium browser by Firefox http://moodeaudio.org/forum/showthread.p...9#pid33369
Since that mod, moOde is just working flawlessly for more than 2 months now, no memory eating chromium zombie anymore. Even the mod reads difficult, it is straight forward. I was at the same difficult decision point you are to go back to an older moOde version or to apply that mod. For me it was the right decision. The only thing you should avoid to do - after you changed from chromium to firefox - is to upgrade to a newer moOde version as this probably would ruin your setup.
Thanks for the suggestion! If that’s known to work, I think I’ll follow that. Do you have it running on a 1-GB Pi?
I love using and testing every new version of MoOde, I guess I will try new versions and, if the problem is still there, I’ll reapply the modifications.
Or even devs might want to put a toggle in the config screen to select the browser…
Thanks!
Jv
Yes, it is running on a 3B+ with 1GB RAM and using the original 7" touchscreen. I did also successfully test it on a pi4. Your idea with the configurable browser sounds good.