Emby leaking memory, process is taking more than 20G of RAM

[OscarCalvo 0]

I am seeing this in the Event Viewer:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: EmbyServer.exe (8960) consumed 21299441664 bytes, MsMpEng.exe (4128) consumed 324272128 bytes, and svchost.exe (2736) consumed 172748800 bytes.

This started to happen after I did thousands of renames of pictures (and some small number of videos)

Will try to post the log.

Emby is running in a VM with 16G of RAM, almost all of the VM is only to run Emby

Running Emby 4.7.0.60

This is corelated with me doing thousands of file renames that are indexed by Emby on the NAS.

 

[Abobader 3470]

Hello OscarCalvo,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[Luke 42083]

Hi there, please attach the emby server log from when this happened:

Thanks !

[OscarCalvo 0]

[Luke 42083]

Hi there @OscarCalvo, can you please attach the emby server log from when this happened?

Thanks !

[OscarCalvo 0]

embyserver-63788828043.txt

[OscarCalvo 0]

59 minutes ago, Luke said:

Hi there @OscarCalvo, can you please attach the emby server log from when this happened?

Thanks !

I have 10Gb dump that I am trying to analyze with WinDbg. (VS fails to open as using "managed memory diagnostic")

[OscarCalvo 0]

embyserver.txt

Here is another one, this time I left the server doing nothing.

It seems to start consuming RAM after doing "Info LibraryMonitor: Stopping directory watching for path ABC"

[OscarCalvo 0]

Here is the Heap View from the massive 10Gb dump. Most allocated type is TagLib.IFD.IFDStructure

There are so many that VS can only display a "representative sample"

 

Edited May 23, 2022 by OscarCalvo

[OscarCalvo 0]

It seems I can trigger the problem by manually Scanning the library.

The process will start taking a lot of memory while scanning pictures:

2022-05-22 19:24:36.040 Debug App: FolderImageProvider reports change to 631183 - S:\ServerFolders\Pictures\Familia Calvo\2016\05\2016.05.14
2022-05-22 19:24:36.041 Debug App: Running FolderImageProvider for S:\ServerFolders\Pictures\Familia Calvo\2016\05\2016.05.14
2022-05-22 19:24:48.368 Debug App: Running PhotoProvider for S:\ServerFolders\Pictures\Familia Calvo\2016\Hazel OneDrive-S2016-E0217.17.07.52.jpg
 

This explains why I can only see this after doing lots of pictures file renames.

Also, the Tag.IFD.IFDStruture seems to be uses for getting picture metadata.

[Luke 42083]

OK yes that is a third party library that we're using for photo scanning. We'll take a look at it. Thanks.

[jmrotzek 0]

Has there been a resolution for PhotoProvider? I am seeing a memory issue as described in this and other threads.

    2023-05-23 16:54:32.972 Debug App: Running PhotoProvider for /media/Photos/2013/Bill's Visit/20130324_183937.jpg

 

embyserver-63820457833.txt

[Luke 42083]

7 minutes ago, jmrotzek said:

Has there been a resolution for PhotoProvider? I am seeing a memory issue as described in this and other threads.

    2023-05-23 16:54:32.972 Debug App: Running PhotoProvider for /media/Photos/2013/Bill's Visit/20130324_183937.jpg

 

embyserver-63820457833.txt 78.07 kB · 0 downloads

Hi, yes the issue is resolved in the upcoming 4.8 server release. If you need immediate relief either remove your photo library from Emby Server, or try the 4.8 beta channel. Thanks.