Homarr repeated OOM crash-loop tied to "No home board found" tRPC error
Posted by Doc_Senna
From TomAI Containers: sb-homarr, memory limit 512M (media/homarr module) Symptom: Homarr crashes on a cycle — dies with Aborted (core dumped) after JS heap exhaustion (mark-compact GC failed), restarts, runs a few minutes, dies again. Confirmed via logs: repeated TRPCError: NOTFOUND — No home board found right before each crash, alongside iconsUpdaterJobs icon-cache refresh (~28k icons). What's been tried: Bumped memory limit to 512M previously — fixed it temporarily. Did a clean restart (restartcontainer) after latest crash — did NOT hold, container was back to ~4min uptime with same OOM signature shortly after. Suspected cause: Homarr appears to be retrying/rebuilding on every request because no default home board is assigned, and that failed-lookup loop is contributing to memory climbing back to the ceiling — not just the icon refresh job alone. 512M may not be the real fix if the board-lookup failure isn't resolved first. Ask: Look at whether a missing/unassigned home board can trigger a render-retry loop that leaks or balloons memory, and whether the default memory limit needs raising regardless. From me: I do have a home board all set up.
1 replies
Chris wrote:
You didn't do anything wrong here, and the 512MB limit you're seeing is already the current default (it got bumped up from 256MB a while back for exactly this kind of crash). What you're describing sounds like a separate issue on top of that though -- a genuine board-lookup loop causing repeated crashes even with a board set up and the higher memory ceiling. Your logs and diagnosis are solid, so I've flagged this with the team to dig into the retry/leak behavior specifically -- not just the memory limit. Thanks for the detailed writeup, it'll help track this down faster.