So I’m self hosting Immich in docker with Immich frame. I’m running Immich frame on a raspberry pi 4 in chromium (full screen on an 7” touch screen frame) and it works great, until it seems to randomly close chromium. If I reopen chromium it says do I want to restore tab, when I do it just pulls up my Immich frame IP and works like normal again. I am going to look through my docker logs today after work but has anyone else run into this issue before? It is pretty random and it’s been working for a week straight and then randomly the pi will just be on the home screen instead of full screen chromium.

  • JASN_DE@feddit.org
    link
    fedilink
    English
    arrow-up
    12
    ·
    23 hours ago

    randomly the pi will just be on the home screen instead of full screen chromium.

    Sounds a bit like the system running out of RAM and killing off Chromium.

    • system specs?
    • OS?
    • do you monitor your system continually?
    • does Immich itself show any signs of failure? Because reconnect on browser reopen sounds like it keeps working. OR it restarts automatically, but that shouldn’t kill Chromium.
    • ClydapusGotwald@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      22 hours ago

      It’s a 2gb pi 4 running latest pi version trixie.

      Immich and Immich frame are on docker on my HL15 server. Immich itself isn’t going down. I need to check logs for Immich frame.

      Is there a way to make chromium not eat through all the ram? Or maybe I should just try Firefox on the pi?

      • JASN_DE@feddit.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        22 hours ago

        Ah, apparently I misread, I thought Immich was running on the same Pi.

        You could try another browser, but you’ll still have to check other possible sources. RAM usage, system log, etc.

  • frongt@lemmy.zip
    link
    fedilink
    English
    arrow-up
    3
    ·
    19 hours ago

    If the browser crashes, it’s a client side problem. Check the client system logs.