New Jellyfin Server/Web release: 10.11.5

[template326]

The speed of 10.11.1 is slow and 10.11.5 is decent on my setup. However, some of the pages in music album library will not finish loading. It just keeps spinning.

[I-G-1-1]

I am quite curious about the issues describe on this thread. It seems that most of the users with issues have Jellyfin with Windows.
My jellyfin is installed with docker on a Synology NAS and the version 10.11.5 on my test server is really faster than the 10.10.7 on my prod server.
Is there anybody on Linux or docker who experiment troubles?

Proxmox 8.4 running an LXC with Debian 12 and Jellyfin installed trhough apt. Had to revert from 10.11.5 to 10.10.7.

Definitely not a "Windows issue".

[pavichokche]

So far running smoothly for a week or two on Windows 11 Pro, installed over 10.10.7. So there isn't a specific "Windows issue". Rather, I'm guessing, database gremlins caused by people having complex/numerous/massive libraries. Given that my migration only took a minute or two and the installation instructions talked about how it can take hours I guess there is a lot of room for issues to pop up with larger libraries.

[techjunkie]

I'm having a issues with client not being able to log in

when this happens to a client I can not delete the client account until I untick Allow remote connections to this server, then I can delete client

re adding client fixes the login for a while but can happen again after a while

I'm using 10.11.5

[WWWesten]

i added the "looney tunes" collection to my library (which has more than 1,000 animated shorts) scans just stopped working.

Slowdowns due to excessive logging. Place this file logging.json in /jellyfin/config/
{
    "Serilog": {
        "MinimumLevel": {
            "Default": "Warning",
            "Override": {
                "Microsoft": "Warning",
                "System": "Warning"
            }
        },
        "WriteTo": [
            {
                "Name": "Console",
                "Args": {
                    "outputTemplate": "[{Timestamp:HH:mm:ss}] [{Level:u3}] [{ThreadId}] {SourceContext}: {Message:lj}{NewLine}{Exception}"
                }
            },
            {
                "Name": "Async",
                "Args": {
                    "configure": [
                        {
                            "Name": "File",
                            "Args": {
                                "path": "%JELLYFIN_LOG_DIR%//log_.log",
                                "rollingInterval": "Day",
                                "retainedFileCountLimit": 3,
                                "rollOnFileSizeLimit": true,
                                "fileSizeLimitBytes": 100000000,
                                "outputTemplate": "[{Timestamp:yyyy-MM-dd HH:mm:ss.fff zzz}] [{Level:u3}] [{ThreadId}] {SourceContext}: {Message}{NewLine}{Exception}"
                            }
                        }
                    ]
                }
            }
        ],
        "Enrich": [ "FromLogContext", "WithThreadId" ]
    }
}
It is based on /jellyfin/config/config/logging.default.json. The string "Default": "Information", changed to "Default": "Warning",

[giannisg2004]

I am quite curious about the issues describe on this thread. It seems that most of the users with issues have Jellyfin with Windows.
My jellyfin is installed with docker on a Synology NAS and the version 10.11.5 on my test server is really faster than the 10.10.7 on my prod server.
Is there anybody on Linux or docker who experiment troubles?

That's not true. 

I'm on Linux (jellyfin is its own LXC, under Proxmox), and the issues have been apparent from the first release of 10.11.0, and have only slightly improved by 10.11.5.

There are well documented and confirmed issues with:

1. Home Video and Photo libraries
   
2. Music libraries
   
3. Any  library that contains subfolders and where the file structure is not picture-perfect the exact way Jellyfin expects
   
4. Collections, especially larger ones
   
5. Even if you do everything perfectly and work around those issues, say only use Movies and Series libraries, have the file structure exactly right, don't use collections: Library scans (and most other tasks) are still appreciably slower, (anecdotally) by a factor between 5x-10x. Multiple "database locked" errors in the logs, and more importantly: when those errors happen, the interface becomes sluggish or hangs (sometimes for dozens of seconds, sometimes for minutes), and playback stutters or hangs completely. Also, when any scheduled tasks are running, which now are 5-10x longer, you're far more likely to encounter interface hangs.
   

From 4. and 5., it's pretty safe to say, that the new EFcore ORM implemented writes some really inefficient SQL queries in conjunction with the new locking mechanism, leading to massively increased database lock errors. These cause the interface and playback to hang, and scheduled tasks to last much longer.

1. is just neglect/depreciation, 2. and 3. is some bugs that might or might not get fixed depending on how strictly the developer team wants to enforce the desired file structure and if they wanna bother to debug Jellyfin to work acceptably with non-ideal file structures.

All said and done, I'm actually willing to bet the opposite: people that have not encountered these issues are using only a small subset of Jellyfin (just Movies and Series), don't use collections, have potentially smaller libraries and fewer users, so those issues are masked.


I'm attaching a characteristic example of the time it takes for the various scheduled tasks. Running on the exact same media files/libraries, on the exact same hardware.