Emby memory usage is too high under Docker

[seanbuff 1368]

2 hours ago, aaaa123 said:

@Luke @seanbuffHow about it, after all this time, have you solved my high memory usage problem?

4.9 stable has been released now, have you upgraded your system to compare?

[aaaa123 0]

@Luke@seanbuffThe problem persists. I'm using Docker to deploy Emby, and the current version is the latest official version 4.9.1.80. Video playback still consumes memory; both fast-forwarding and playback use memory. Even after closing the webpage, the memory doesn't automatically release; it only releases memory by restarting the container or limiting the container's total memory size. Without limiting it, it continuously consumes memory indefinitely.

[Luke 42470]

HI, we are looking into it. Thanks.

[Bims0n 14]

What is your DSM version? Your docker UI seems kinda old, maybe try updating this package + your DSM version

[aaaa123 0]

1 minute ago, Bims0n said:

What is your DSM version? Your docker UI seems kinda old, maybe try updating this package + your DSM version

I am using DSM 7.1.1-42962 Update 2.

[youflyang 2]

4.9.3也是同样的情况，只要播放一会儿，内存就直接占满8G，然后后续的请求卡顿，只有重启才能缓解。

[Luke 42470]

On 2/26/2026 at 10:54 PM, youflyang said:

4.9.3也是同样的情况，只要播放一会儿，内存就直接占满8G，然后后续的请求卡顿，只有重启才能缓解。

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[17732 21]

On 3/5/2026 at 10:27 AM, Luke said:

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

This is a very serious problem, but I don't think the Emby developers are taking it seriously. My friends all experienced severe memory usage issues after upgrading to version 4.9. I've upgraded to version 4.9.5.0, and the memory usage has reached 7.3GB. My NAS has 16GB of RAM and I can still use it, but what will happen to us users if it continues to consume so much RAM? I want to ask the Emby developers, have you considered this problem? Many NAS devices with very little RAM will be unable to use Emby services. Don't you Emby developers find this problem strange? Why was it normal in version 4.8, and why are users only experiencing this problem after upgrading to version 4.9? Emby developers, I want to tell you that this is a very serious matter, not a trivial one. Okay, even if I've sent you the logs, if your developers don't seriously analyze this problem from version 4.9 onwards, it will forever remain with Emby.

embyserver.txt