07-29-2021, 05:55 PM
@Sehnsucht
Enabling the local display function spins up a bunch of Chromium browser processes. Consult the linked post and read the code (start with /home/pi/.xinitrc). We don't know yet why this brain-eating zombie behavior gets triggered. I only scratched the surface with my testing. Any test data you can contribute which points to a root cause would be great.
As well, in private Testing Team discussions I reported on the failure occurring when I tried using Vivaldi as an alternative----not surprising since it shares the same rendering engine---as well as when I tried different versions of Chromium. There are other browsers available for RaspiOS but I haven't tried using them for moOde's local display.
@jv275475
I never saw this issue with an official DSI display, only with an HDMI display, but that's not definitive.
Pretty much all my gear is packed away at the moment (just one player with headphones to while away time in our extended stay hotel room when I get bored with Olympics coverage) so no testing possible.
Obviously, we want all features of moOde to Just Work™. Some months ago, @Tim Curtis had suggested to the Test Team that a brute-force solution might be useful while we try to sort out the local display issue with Chromium eating memory. Looks like it's time to revisit that proposition. It's ugly (screen flashing, etc., while Chromium re-initializes) but it's easy.
Regards,
Kent
Enabling the local display function spins up a bunch of Chromium browser processes. Consult the linked post and read the code (start with /home/pi/.xinitrc). We don't know yet why this brain-eating zombie behavior gets triggered. I only scratched the surface with my testing. Any test data you can contribute which points to a root cause would be great.
As well, in private Testing Team discussions I reported on the failure occurring when I tried using Vivaldi as an alternative----not surprising since it shares the same rendering engine---as well as when I tried different versions of Chromium. There are other browsers available for RaspiOS but I haven't tried using them for moOde's local display.
@jv275475
I never saw this issue with an official DSI display, only with an HDMI display, but that's not definitive.
Pretty much all my gear is packed away at the moment (just one player with headphones to while away time in our extended stay hotel room when I get bored with Olympics coverage) so no testing possible.
Obviously, we want all features of moOde to Just Work™. Some months ago, @Tim Curtis had suggested to the Test Team that a brute-force solution might be useful while we try to sort out the local display issue with Chromium eating memory. Looks like it's time to revisit that proposition. It's ugly (screen flashing, etc., while Chromium re-initializes) but it's easy.
Regards,
Kent
