Jump to content

Emby Server Memory Leak


h45e

Recommended Posts

Hi, It looks like I am having a memory leak causing Emby to pause the playback for a while then restart or totally kill the playback, I can only fix this with a force close of emby or a complete reboot.

I am currently running 4.7.5.0

I have tried the solutions of

https://emby.media/community/index.php?/topic/37823-high-memory-usage-normal/

Can someone help me 

I currently have 2597 Movie Items and 736 TV Items if that helps?

Capture.PNG

Capture2.PNG

embyserver.txt

Link to comment
Share on other sites

53 minutes ago, h45e said:

Good news it has just happened again... Here is the latest logs. 

embyserver.txt 1.87 kB · 0 downloads embyserver-63792846485.txt 16.32 kB · 0 downloads

Regarding the database locked errors in your log, I would take a look at this and see if it helps: https://support.emby.media/support/solutions/articles/44002210894-corrupt-database

Thanks.

Link to comment
Share on other sites

Hi, 

Tried the data base fix but that didnt work. But i decided to try the portable version and "installed" it on my c drive. It is currently working atm. Going to do more stress testing also.

  • Thanks 1
Link to comment
Share on other sites

visproduction

I noticed this:
2022-07-14 12:57:16.345 Error PortMapper: Error getting nat device info from 192.168.0.141

Similar issue to another forum post: 
 

In this post, Luke also suggests another forum post:
 https://support.emby.media/support/solutions/articles/44002137137-remote-setup

===
Also tvdb errors happen a lot.  Maybe just turn that source off.  They may have updated their API they have heavy traffic or server hit limits.  See: https://thetvdb.com/api-information

===

Old background image that is gone, but still being called?
 

2022-07-14 13:05:27.854 Error App: Image Provider - Error reading image tag for 
\\192.168.0.100\Multimedia\Pictures\General\2011 Calander\Happy_Birthday.jpg

===


Many xmlsoap.org entries at the end of the log:
 

2022-07-14 13:27:01.536 Error HttpClient: <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" 
                                                      s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault>
  <faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0">
  <errorCode>718</errorCode><errorDescription>ConflictInMappingEntry</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>


===
Hope that helps.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...