Jellyfin Forum
v10.11.0: Home Videos libraries take *extremely* long to load - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: v10.11.0: Home Videos libraries take *extremely* long to load (/t-v10-11-0-home-videos-libraries-take-extremely-long-to-load)



v10.11.0: Home Videos libraries take *extremely* long to load - Vitosi4ek - 2025-10-22

Hi everyone. I'm using Jellyfin Server 10.11.0 in a Docker container on a TrueNAS 25.04 box (as a TrueNAS community app from the marketplace). Yesterday upgraded to the latest version and the process seemed to work fine (it only wiped my TV channels, but luckily I had them set up via Dispatcharr and it was a matter of one click to re-import them). 

The big problem, though, is that libraries became much slower to load. It's most pronounced on "Home Videos" libraries, in particular my archive of YouTube videos with over 16,000 items. Prior to the update it loaded near-instantaneously, just like all the other libraries, but now it can easily take over 2-3 minutes just to load the root folder (and then additional time to load every subfolder). It seems like the load time is proportional to the amount of items in the folder I'm trying to open - I have another Home Videos library with around 2,000 items, it takes around 10 seconds to load it initially and then it varies. This is more palatable, but still a big downgrade from how it used to be. The behavior is the same on both the web client, all the mobile clients and the Android TV app.

The normal Movies and TV Shows libraries seem to not be affected nearly as badly (though it still takes 5-7 seconds to load all seasons of a TV show with 1,500 episodes).

Unfortunately the logs don't seem to register the act of opening a library at all, but I do notice that every time I do it, 1 thread on my 12-thread CPU (Ryzen 5600G) gets pinned at or near 100% until the load finishes. Neither the SSD that hosts the container nor the drives hosting the media files show any meaningful activity during that time.

Removing the library and re-adding it from scratch didn't help. Neither did a full rescan of the whole media vault. In fact, after the re-add the behavior of the 16,000 item library seems to have changed for the worse - it now doesn't load at all, and the CPU pins 1 thread for around 1 minute before giving up. Nothing crashes and I can exit out no problem, but the library simply gets stuck on the loading circle with no progress.

Hopefully this is just a bug in the new version that can be fixed, but if not, another question - considering the huge under-the-hood changes and the library migration, is it even safe to use the "Roll Back" function in TrueNAS to revert to 10.10.7?


RE: v10.11.0: Home Videos libraries take *extremely* long to load - kandykarter - 2025-10-22

This happens with collections for me, also. It's pretty frustrating because I've painstakingly created almost a hundred custom collections to make discovery of movies in a huge library possible, and now it's a colossal pain in the ass to use.


RE: v10.11.0: Home Videos libraries take *extremely* long to load - paulc - 2025-10-22

I experience this with Mixed libraries and libraries marked as 'Other' in the admin library panel. I've let it stay open on the web for 20 minutes or so but on Roku, it takes around 1 minute before they appear. Doesn't matter the library size of mixed, homes, (other, etc), takes just under one minute. Interesting, items are displayed on the home screen and items are discovered in search in normal fashion, time unaffected. (Setup Windows 10 non-docker)


RE: v10.11.0: Home Videos libraries take *extremely* long to load - Vitosi4ek - 2025-10-22

(8 hours ago)paulc Wrote: items are displayed on the home screen and items are discovered in search in normal fashion, time unaffected. (Setup Windows 10 non-docker)

Can confirm that too. Searching for items in my 16,000 item library works perfectly and immediately, so the library itself is most likely indexed and parsed correctly.