Possible memory leak on Linux version? Memory usage climbing 100MB per hour even when idle. Windows version not affected.

backuprepo commented

2025-12-22 04:07:44 +01:00

Owner

Originally created by @robotreto on GitHub (Oct 17, 2024).

This issue respects the following points:

This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
This issue is not already reported on GitHub (I've searched it).
I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
I agree to follow Jellyfin's Code of Conduct.
This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

There are similar issues reported on suspected memory leaks of jellyfin server in the past couple of months :
https://github.com/jellyfin/jellyfin/issues/11551
https://github.com/jellyfin/jellyfin/issues/11588

However it could not be really reproduced by the developers. As my jellyfin server on a QNAP too is affected with ever-growing memory usage, and as I am myself a programmer, I decided to look into the issue and downloaded the source (master 10.10.0) and build the server under VS2022. However I could not really reproduce the issue, memory usage remained stable, at least under Windows 11. I used the exact same media libraries as on my QNAP, 11'000 MP4/MKV, 60'000 JPG and 10'000 MP3, about 18TB in total. So it seems it depends whether the server runs under Linux or Windows.
I started both servers at the same time, and monitored memory usage over the next 16 hours :

While running under Windows, memory-consumption is reasonable and also stable, even dropping when idle (which proves the function of the Garbage Collector), under Linux the usage is ever increasing, even when the server is idle, about 50-100MB per hour.
This difference between Windows and Linux could explain why the developers could not duplicate the issue, because they are probably developing under Windows, where the issue is not present.

This behavior has been reported also by other users, especially running jellyfin under docker. Some users report memory usage > 20 GB over time. Sadly all issues have been closed so far, with the problem still existing.

Reproduction steps

Configure a Linux server and a Windows Server, with the exact same media libraries.
Start them at the exact same time
over the next 16 hours, interact with both servers the same way, browse the same libraries and start same movies.
record the memory usage of both servers and compare them.

What is the current bug behavior?

At some point, the memory will be exhausted and the server will be terminated with out-of-memory exception. This could take many weeks, depending on how much RAM the host has.

What is the expected correct behavior?

Linux version should have a similar memory usage pattern as the windows version, and certainly not run into a out-of-memory exception after a certain time.

Jellyfin Server version

Master

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.9.10

Specify the build version

10.9.10, QNAP port by pdulvp

Environment

Windows server running under VS2022 debugger,  Windows is a regular 11 23H2
Linux-Version : QNAP QTS 5.2.0.2860, running jellyfin natively (QNAP port by pdulvp), not as docker

Jellyfin logs

no relevant logs as both servers behave normally, with the exception of ever increasing memory usage of the linux version.

FFmpeg logs

No response

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

One thing we have to be aware of: As the QNAP version is older than the current master (10.10.0), it might be that I compared apples and pears. Maybe the issue has already been fixed in 10.10.0.

And no, I am not a Linux-hater, I use Linux myself on some machines, but I have to admit I dont know how to program/debug under Linux.

Originally created by @robotreto on GitHub (Oct 17, 2024). ### This issue respects the following points: - [X] This is a **bug**, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found [here](https://jellyfin.org/contact/). - [X] This issue is **not** already reported on [GitHub](https://github.com/jellyfin/jellyfin/issues?q=is%3Aopen+is%3Aissue) _(I've searched it)_. - [X] I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue. - [X] I agree to follow Jellyfin's [Code of Conduct](https://jellyfin.org/docs/general/community-standards.html#code-of-conduct). - [X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one. ### Description of the bug There are similar issues reported on suspected memory leaks of jellyfin server in the past couple of months : https://github.com/jellyfin/jellyfin/issues/11551 https://github.com/jellyfin/jellyfin/issues/11588 However it could not be really reproduced by the developers. As my jellyfin server on a QNAP too is affected with ever-growing memory usage, and as I am myself a programmer, I decided to look into the issue and downloaded the source (master 10.10.0) and build the server under VS2022. However I could not really reproduce the issue, memory usage remained stable, at least under Windows 11. I used the exact same media libraries as on my QNAP, 11'000 MP4/MKV, 60'000 JPG and 10'000 MP3, about 18TB in total. So it seems it depends whether the server runs under Linux or Windows. I started both servers at the same time, and monitored memory usage over the next 16 hours : ![Memory Chart](https://github.com/user-attachments/assets/2d286ae9-0c29-46ad-aa8c-bba8dcc88c93) While running under Windows, memory-consumption is reasonable and also stable, even dropping when idle (which proves the function of the Garbage Collector), under Linux the usage is ever increasing, even when the server is idle, about 50-100MB per hour. This difference between Windows and Linux could explain why the developers could not duplicate the issue, because they are probably developing under Windows, where the issue is not present. This behavior has been reported also by other users, especially running jellyfin under docker. Some users report memory usage > 20 GB over time. Sadly all issues have been closed so far, with the problem still existing. ### Reproduction steps 1) Configure a Linux server and a Windows Server, with the exact same media libraries. 2) Start them at the exact same time 3) over the next 16 hours, interact with both servers the same way, browse the same libraries and start same movies. 4) record the memory usage of both servers and compare them. ### What is the current _bug_ behavior? At some point, the memory will be exhausted and the server will be terminated with out-of-memory exception. This could take many weeks, depending on how much RAM the host has. ### What is the expected _correct_ behavior? Linux version should have a similar memory usage pattern as the windows version, and certainly not run into a out-of-memory exception after a certain time. ### Jellyfin Server version Master ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number 10.9.10 ### Specify the build version 10.9.10, QNAP port by pdulvp ### Environment ```markdown Windows server running under VS2022 debugger, Windows is a regular 11 23H2 Linux-Version : QNAP QTS 5.2.0.2860, running jellyfin natively (QNAP port by pdulvp), not as docker ``` ### Jellyfin logs ```shell no relevant logs as both servers behave normally, with the exception of ever increasing memory usage of the linux version. ``` ### FFmpeg logs _No response_ ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information One thing we have to be aware of: As the QNAP version is older than the current master (10.10.0), it might be that I compared apples and pears. Maybe the issue has already been fixed in 10.10.0. And no, I am not a Linux-hater, I use Linux myself on some machines, but I have to admit I dont know how to program/debug under Linux.

backuprepo

2025-12-22 04:07:44 +01:00

closed this issue
added the
bug

downstream
labels

backuprepo commented

2025-12-22 04:07:49 +01:00

Author

Owner

@darthShadow commented on GitHub (Oct 17, 2024):

Not sure how QNAP does it's packaging, but can you verify whether you have the MALLOC_TRIM_THRESHOLD_ set for your Jellyfin Environment (Source: 6beda5c94f/debian/conf/jellyfin (L28))?

This was specifically added to partially address memory leaks seen earlier: https://github.com/jellyfin/jellyfin/pull/10454

There are a bunch of memory issues related to the dotnet runtime on Linux in their GH tracker if you want to take a look to see if any mentioned settings help control the memory usage. One example of such settings: https://github.com/dotnet/runtime/issues/49317#issuecomment-1719158573

@darthShadow commented on GitHub (Oct 17, 2024): Not sure how QNAP does it's packaging, but can you verify whether you have the `MALLOC_TRIM_THRESHOLD_` set for your Jellyfin Environment (Source: https://github.com/jellyfin/jellyfin-packaging/blob/6beda5c94f15390bc0512782cbbf6cdafd87d04d/debian/conf/jellyfin#L28)? This was specifically added to partially address memory leaks seen earlier: https://github.com/jellyfin/jellyfin/pull/10454 There are a bunch of memory issues related to the dotnet runtime on Linux in their GH tracker if you want to take a look to see if any mentioned settings help control the memory usage. One example of such settings: https://github.com/dotnet/runtime/issues/49317#issuecomment-1719158573

backuprepo commented

2025-12-22 04:07:50 +01:00

Author

Owner

@nyanmisaka commented on GitHub (Oct 17, 2024):

The community maintained pdulvp/jellyfin-qnap misses this environment variable.

@nyanmisaka commented on GitHub (Oct 17, 2024): The community maintained [pdulvp/jellyfin-qnap](https://github.com/search?q=repo%3Apdulvp%2Fjellyfin-qnap%20MALLOC_TRIM_THRESHOLD_&type=code) misses this environment variable.

backuprepo commented

2025-12-22 04:07:51 +01:00

Author

Owner

@felix920506 commented on GitHub (Oct 17, 2024):

Closing this as this is an issue caused by a 3rd party package.

@felix920506 commented on GitHub (Oct 17, 2024): Closing this as this is an issue caused by a 3rd party package.

backuprepo commented

2025-12-22 04:07:52 +01:00

Author

Owner

@robotreto commented on GitHub (Oct 17, 2024):

Which 3rd party package exactly ? If you mean QNAP, then please know the same momory runaway was also reported under other linux versions, including docker containers, so the QNAP package is not to blame.

@robotreto commented on GitHub (Oct 17, 2024): Which 3rd party package exactly ? If you mean QNAP, then please know the same momory runaway was also reported under other linux versions, including docker containers, so the QNAP package is not to blame.

backuprepo commented

2025-12-22 04:07:54 +01:00

Author

Owner

@soakes commented on GitHub (Oct 17, 2024):

Just chiming in here, even adding in MALLOC_TRIM_THRESHOLD_=131072 ENV as shown in https://github.com/jellyfin/jellyfin/issues/11551 still OOM's. Even if @robotreto goes and adds this ENV in, it will not stop whats happening from happening. I really don't understand why this problem keeps being closed.

@soakes commented on GitHub (Oct 17, 2024): Just chiming in here, even adding in `MALLOC_TRIM_THRESHOLD_=131072` ENV as shown in https://github.com/jellyfin/jellyfin/issues/11551 still OOM's. Even if @robotreto goes and adds this ENV in, it will not stop whats happening from happening. I really don't understand why this problem keeps being closed.

backuprepo commented

2025-12-22 04:07:54 +01:00

Author

Owner

@felix920506 commented on GitHub (Oct 17, 2024):

#11551 is a totally different issue from this one

@felix920506 commented on GitHub (Oct 17, 2024): #11551 is a totally different issue from this one

backuprepo commented

2025-12-22 04:07:55 +01:00

Author

Owner

@robotreto commented on GitHub (Oct 17, 2024):

agree, I added export MALLOC_TRIM_THRESHOLD_=131072 to the startup script, memory usage jumped from 500 to 2400 GB in just 4 hours, completely idling, so this hack did not help anything.
And agree, why this memory runaway is being closed without further investigation.

@robotreto commented on GitHub (Oct 17, 2024): agree, I added `export MALLOC_TRIM_THRESHOLD_=131072` to the startup script, memory usage jumped from 500 to 2400 GB in just 4 hours, completely idling, so this hack did not help anything. And agree, why this memory runaway is being closed without further investigation.

backuprepo commented

2025-12-22 04:07:57 +01:00

Author

Owner

@soakes commented on GitHub (Oct 17, 2024):

@felix920506 Really? Why are you saying that? can you englighten me on your thinking here?

@robotreto mentions that, there is possibly a leek as the RAM on the Linux version are just growing and growing without releasing it but this is not happening with Windows. This is exactly the same as the other issue which was also closed.

@soakes commented on GitHub (Oct 17, 2024): @felix920506 Really? Why are you saying that? can you englighten me on your thinking here? @robotreto mentions that, there is possibly a leek as the RAM on the Linux version are just growing and growing without releasing it but this is not happening with Windows. This is exactly the same as the other issue which was also closed.

backuprepo commented

2025-12-22 04:07:58 +01:00

Author

Owner

@robotreto commented on GitHub (Oct 17, 2024):

Not sure how QNAP does it's packaging, but can you verify whether you have the MALLOC_TRIM_THRESHOLD_ set for your Jellyfin Environment (Source: 6beda5c94f/debian/conf/jellyfin (L28))?

Tried to add that env variable to the startup script, restarted server, but it made no difference.

@robotreto commented on GitHub (Oct 17, 2024): > Not sure how QNAP does it's packaging, but can you verify whether you have the `MALLOC_TRIM_THRESHOLD_` set for your Jellyfin Environment (Source: https://github.com/jellyfin/jellyfin-packaging/blob/6beda5c94f15390bc0512782cbbf6cdafd87d04d/debian/conf/jellyfin#L28)? > Tried to add that env variable to the startup script, restarted server, but it made no difference.

Rows
Columns

Possible memory leak on Linux version? Memory usage climbing 100MB per hour even when idle. Windows version not affected. #6359

This issue respects the following points:

Description of the bug

Reproduction steps

What is the current bug behavior?

What is the expected correct behavior?

Jellyfin Server version

Specify commit id

Specify unstable release number

Specify version number

Specify the build version

Environment

Jellyfin logs

FFmpeg logs

Client / Browser logs

Relevant screenshots or videos

Additional information