Ross Patterson
Ross Patterson
My first observed symptom was the slow startup causing `HEALTHCHECK` failures, so see [my comment there](https://github.com/jellyfin/jellyfin/issues/10225#issuecomment-2212522937) if you want more context.
> Gonna need to see those nfo files Sorry, they're gone now, but also I wouldn't share them for privacy reasons. But I'd be happy to elaborate on the details...
> my is same.when the library scan, a huge ram on use, untill full ram used,and jellyfin stop See [my comment in another issue that I linked to in my...
> If you don't want to share one from your library then I suggest you manufacture one with random data in a text editor or something and provide it. From...
Still waiting for follow up on the steps to reproduce.
> Proper documentation is being worked on. This would have helped me a lot. I have been struggling with this from *both* ends. Firstly, I've been having lots of issues...
I wrote a little Python script to clean this up in my library. It guesses that resume time codes are artificial when more than 10 movies have the same resume...
> The number of movies in the `Resumable` filter went down from half of the library to just a handful and the ones with remaining resume time codes look correct...
> I've re-run my reset script and I'll try to keep a closer eye on when this recurs to see if I can correlate it to any potential triggers. I...
> Some of those have `On application startup` triggers, so next I'll repair the resume progress again and restart the application and see if the issue recurs. These plugins report...