Navidrome Daily: Closing the Jellyfin Memory Leaks
A week-long push to make Navidrome's Jellyfin API safe for real-world sync clients closed a series of out-of-memory holes in playlists, searches, and library browsing, while also shipping a new AudioMuse-AI compatible sonic feature and a UI tooling fix.
Duration: PT2M25S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-07-16T10:00:47Z
- Audio duration: PT2M25S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good evening. It's July 16th, and tonight's story is about one API finally getting hardened end to end.
The dominant theme this week: Jellyfin compatibility had a class of out-of-memory bugs, and the team ran them down systematically rather than patching one and moving on. It started with PR 5783, which found that an unbounded library sync request could peak at over one and a half gigabytes of memory on a large…
That same rigor extended to correctness, not just memory. PR 5788 found that Navidrome had been ignoring the "recursive" parameter entirely — always answering as if it were true, which meant sync clients like Finamp were pulling every track twice. A follow-up commit found the album filter had the same problem:…
Alongside the hardening, PR 5782 shipped something new: sonic-similarity endpoints compatible with AudioMuse-AI, so Jellyfin clients like Finamp and Feishin get similarity features natively, no external plugin required.
Separately, Gr3q's PR 5787 fixed the UI type-checking command, which had silently been doing nothing due to a missing build flag.
What to remember: if you're touching the Jellyfin API, assume large-library and sync-client behavior needs explicit testing…