+1 here
Same here, on direct mode for myself, not tried library mode.
We’ve been reviewing a few reports that have come in, and it looks like the issue is on Jellyfin’s side. When opening a series, we request a list of seasons, but for many shows, the server now responds significantly slower than in previous versions. This also affects fetching time in Library mode.
Presumably a fix should come from Jellyfin, but we’re going to keep digging into potential options here.
5 Likes
Thanks. What’s every other unaffected client doing?
1 Like
Appreciate the efforts here James! The new database implementation on Jellyfin’s side definitely needs some fine tuning from them. One thing I would be curious on though is how other projects are loading and not having issues and maybe taking a peak at their implementation. The one that comes to mind for me is Streamyfin ( GitHub - streamyfin/streamyfin: A modern Jellyfin client built with Expo ).
1 Like
Depending on how clients interact with Jellyfin they may or may not be affected so we may need to adjust how Infuse interacts with Jellyfin if a database fix on their side isn’t forthcoming.
3 Likes
Even just knowing what other clients do, and communicating it to Jellyfin’s people, can help them with their fix if they feel inclined to do something about this.
same here, also when playing a video the jellyfin log spams every second this
[2025-10-31 17:22:25.496 +00:00] [ERR] [54] Emby.Server.Implementations.Session.SessionManager: Error reporting playback progress
System.MissingMethodException: Method not found: ‘System.Collections.Generic.List`1<Jellyfin.Data.Entities.User> MediaBrowser.Controller.Library.PlaybackProgressEventArgs.get_Users()’.
at Jellyfin.Plugin.PlaybackReporting.EventMonitorEntryPoint.SessionManager_PlaybackProgress(Object sender, PlaybackProgressEventArgs e)
at Emby.Server.Implementations.Session.SessionManager.OnPlaybackProgress(PlaybackProgressInfo info, Boolean isAutomated)
at MediaBrowser.Controller.Session.SessionInfo.OnProgressTimerCallback(Object state)
looks like Infuse tries to call some api method that doesn’t exist anymore in 10.11.1
This one seems different. These logs show an error that occurs inside the server’s own code. If we were calling a non-existent API — it would appear during HTTP request parsing instead of a message like this. This is also unrelated to the InfuseSync plugin — as it doesn’t use any of the callbacks mentioned in the logs. Presumably, this issue would occur with any client — not just Infuse — including the web interface when the server receives playback progress updates.
FWIW, we’re not seeing this locally, and the “missing” method is actually still present in the Jellyfin source code. It seems something may have gone wrong with this server or the upgrade process.
Not sure if it helps, but messing around with the API calls I see Infuse performing seems to indicate that including the field “People” in pretty much all API calls drastically increases the response time. If you omit that field, the API is much quicker. E.g.:
- Episode View: 4.2s → 0.14s
- Next Up (Shows): 6.4s → 1.7s
It does seem like a regression from Jellyfin, but I also don’t see the native WebUI doing that call. It seems the native WebUI just does the following on the Show Item ID (not the Episode ID), which returns all the People for the show:
/Users/bcbaa15ab3f24fb5a49a8b7fb50b1e97/Items/baa94152cdaee0f36fa21d231773f660
7 Likes
Issue persists in Jellyfin 10.11.2/Infuse 8.3
thanks, it was indeed the “Playback Reporting” plugin which didn’t update unlike the others.
1 Like
@MetalSnake - Did updating to v17 ( Release Version 17 · jellyfin/jellyfin-plugin-playbackreporting · GitHub ) fix the issue? I’ve held off on upgrading to 10.11 until I saw this was resolved. Thx
Even though it solved the problem for MetalSnake, the issue described here is a different one. For example, I don’t have the Playback Reporting plugin installed at all. I think anekdotos provided a very important clue there.
It fixed the issue I described above. I thought it was related to the slow loading times but it wasn’t.
Also the latest Infuse beta apparently has a fix for the slow loading times.
Got it; I’ll continue to wait. Thank you both
So there’s already a fix in the beta that might go live soon? You just made my day.