Can ImmichFrame run smoothly on a Raspberry Pi Zero 2 W? WPE WebKit swap growth
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing the ImmichFrame playback configuration and its photo cycling behavior; the issue does not name specific files or tests. Reproduce the reported swap growth on a Raspberry Pi Zero 2 W if available, comparing ImmichFrame playback with the about:blank baseline. Done means identifying whether ImmichFrame settings can reduce memory growth and whether playback remains stable over several hours.
Written by the indexing model from the issue text.
Description
Setup
- Raspberry Pi Zero 2 W (512 MB RAM), Raspberry Pi OS Trixie (64-bit)
- Cog 0.18.4 / WPE WebKit, Wayland/labwc, software rendering
- ImmichFrame 1.0.39.0 running in Docker on a Synology NAS
- Pi displays only the ImmichFrame web interface
- Single-image layout, image zoom/pan disabled, transitions reduced
Problem
ImmichFrame runs smoothly on a PC, but on the Pi Zero 2 W it becomes sluggish and occasionally appears frozen.
Disabling image zoom significantly improved CPU usage, but WPE WebKit’s memory usage keeps growing:
Test WPE WebKit swap usage
ImmichFrame, ~3 minutes 63 MiB
ImmichFrame, ~17 minutes 290 MiB
ImmichFrame, ~41 minutes 878 MiB
about:blank, ~10 minutes 16 MiB
The Pi has 415 MiB usable RAM and 2 GiB swap. During ImmichFrame playback, total swap usage exceeded 1 GiB. The browser process appears to accumulate memory as the slideshow runs.
Questions
- Is the Raspberry Pi Zero 2 W powerful enough for smooth, stable ImmichFrame playback?
- Is there a recommended lightweight browser or kiosk setup for this hardware?
- Are there any settings to reduce memory growth when cycling through photos?
- Has anyone successfully run ImmichFrame on a Zero 2 W for several hours without restarting the browser?
Any recommendations or experiences would be greatly appreciated. Thanks!
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 121
- Avg merge
- 18d 20h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from immichFrame/ImmichFrame
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
immichFrame/ImmichFrame#735 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
immichFrame/ImmichFrame#733 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
immichFrame/ImmichFrame#732 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 22/100
immichFrame/ImmichFrame#731 · 1 reaction ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
immichFrame/ImmichFrame#729 ·
All issues in immichFrame/ImmichFrame
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
dotnet/EntityFramework.Docs#5521 ·
Maintainers usually reply within 1 day
-
Feature needs response
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Adyen/adyen-dotnet-api-library#1907 ·
Maintainers usually reply within 5 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dimitar-radenkov/Pointframe#318 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DotHarness/dotcraft#546 ·
Maintainers usually reply within 1 day
-
a-corriger bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
christian-raj/S-Aloha#303 · 1 comment ·