dbowles1975 25 Posted July 23, 2017 Posted July 23, 2017 (edited) I used to have this issue when I ran Emby as service. I run it at start up now and I haven't had this issue since. I also noticed that memory usage would creep up the longer the server had been running so I do a scheduled restart (just the server application, not the PC itself) every morning at 4:00AM just in case. Memory usage stays in the 200MB-300MB range even during heavy use. I don't use any DLNA features. Edited July 23, 2017 by dbowles1975
jnheinz 17 Posted July 23, 2017 Posted July 23, 2017 Rebooting daily should be totally unnecessary for the record. That is what IT people do to mitigate problems that there are no solutions for.
jnheinz 17 Posted July 23, 2017 Posted July 23, 2017 I caught the Emby Server process consuming almost 3GB of RAM. It has been approximately 96 hours since the last reboot. Should I post 4 days worth of server logs? This is with DLNA disabled.
jnheinz 17 Posted July 23, 2017 Posted July 23, 2017 (edited) Here's my server logs dating back to the last reboot on Thursday evening at 9PM. The small log beginning 15 minutes ago is after the most recent reboot. Let me know what you would like for me to try. @@Luke , I had debug logging on too.. or should have, I believe. I turned it on when I realized I had a problem. sparc-memory-leak-logs.zip Edited July 23, 2017 by jnheinz
Luke 42077 Posted July 23, 2017 Posted July 23, 2017 Ok please try removing the Statistics, Kodi Sync and Autoboxset plugins and see if that has an impact. Thanks.
jnheinz 17 Posted July 23, 2017 Posted July 23, 2017 Ok please try removing the Statistics, Kodi Sync and Autoboxset plugins and see if that has an impact. Thanks. Will do. For the record, I've had Kodi Sync & Autoboxset for quite awhile. Statistics is relatively new, installed maybe 2 months ago. I will remove all 3 & reboot this evening.
Luke 42077 Posted July 23, 2017 Posted July 23, 2017 Probably trakt too. I can see some areas for improvement in the plugin. I will do a couple of the quick ones but hopefully a contributor will come forward and spend a bit more time with it.
Luke 42077 Posted July 23, 2017 Posted July 23, 2017 And also update to the latest version of Emby Server, because i see you're still on 3.2.24 and hadn't updated to 3.2.25 yet. There is now 3.2.26. Thanks.
jnheinz 17 Posted July 23, 2017 Posted July 23, 2017 @@Luke , Ok, thanks. I will update to 3.2.26 & remove Trakt as well.
Luke 42077 Posted July 23, 2017 Posted July 23, 2017 Thanks for the feedback. I've also pushed a trakt update with some minor changes.
jnheinz 17 Posted July 24, 2017 Posted July 24, 2017 Removed all discussed plug-ins, including trakt. Updated to 3.2.26. Sent for a reboot. I'll check back in a few days.
Untoten 306 Posted July 24, 2017 Posted July 24, 2017 (edited) I disabled DLNA, did not resolve the issue, I will update to .26 and provide an update in a few days. @@Luke, I cannot upload my logs, as they are 9gb which makes them 1 - unredactable and 2 - I doubt this forum allows 9gb file uploads, so again, something out of my control. I have now made an FR to control log size, which will probably be 'monitored'.}https://emby.media/community/index.php?/topic/49336-fr-control-log-size/ Edited July 24, 2017 by Untoten
jnheinz 17 Posted July 25, 2017 Posted July 25, 2017 (edited) End of day 1.. DLNA disabled, removed trakt, Emby Sync, AutoBoxSet & Statistics plugins. Updated to 3.2.26 & rebooted @ 7/23 @ 10PM CST. Edited July 25, 2017 by jnheinz
parrish 22 Posted July 25, 2017 Author Posted July 25, 2017 (edited) I finally had to resort to creating a scheduled task to shut down the Emby service, wait 5 minutes (since it takes a few minutes for the Emby service to actually shut down once you tell it to shut down), then restart the service. I have that task set to run every day at 8am. Definitely not a fix- just a work around. Edited July 25, 2017 by parrish 1
Luke 42077 Posted July 25, 2017 Posted July 25, 2017 End of day 1.. DLNA disabled, removed trakt, Emby Sync, AutoBoxSet & Statistics plugins. Updated to 3.2.26 & rebooted @ 7/23 @ 10PM CST. Thanks for the feedback.
Untoten 306 Posted July 25, 2017 Posted July 25, 2017 I finally had to resort to creating a scheduled task to shut down the Emby service, wait 5 minutes (since it takes a few minutes for the Emby service to actually shut down once you tell it to shut down), then restart the service. I have that task set to run every day at 8am. Definitely not a fix- just a work around. Care to share the method?
Spotta 6 Posted July 25, 2017 Posted July 25, 2017 Yep, same issue here, this was last night - This morning I couldn't even remote in and had to remotely reboot. my logs - https://www.dropbox.com/sh/rdzumqp2i19a6nv/AACFtsACcvjQdHy0vRzwrJKfa?dl=0
Untoten 306 Posted July 25, 2017 Posted July 25, 2017 Yep, same issue here, this was last night - This morning I couldn't even remote in and had to remotely reboot. my logs - https://www.dropbox.com/sh/rdzumqp2i19a6nv/AACFtsACcvjQdHy0vRzwrJKfa?dl=0 Did you try disabling DLNA? So far mine has been ~1gb it seems to alleviate this issue, which sucks for my playstation/xbox users.
Spotta 6 Posted July 25, 2017 Posted July 25, 2017 yep, disabled it this morning after reading through this thread. lets hope it does the job.
Spotta 6 Posted July 25, 2017 Posted July 25, 2017 after 7 hours uptime, so I guess it made no difference. trying plugins now.
jnheinz 17 Posted July 25, 2017 Posted July 25, 2017 Day 1.5 (36 hours since changes & last reboot) .. DLNA disabled, removed trakt, Emby Sync, AutoBoxSet & Statistics plugins. Updated to 3.2.26 & rebooted @ 7/23 @ 10PM CST. Starting to creep upward towards a half gig. I don't think it's done any actual transcoding, just a few direct play through HTTP I believe. Will update tonight.
jnheinz 17 Posted July 25, 2017 Posted July 25, 2017 (edited) I have created a data collector set in Performance Monitor to log the Private Bytes of the Emby Server process every 15 seconds to aid in long-term visualization. Edited July 25, 2017 by jnheinz
dbowles1975 25 Posted July 25, 2017 Posted July 25, 2017 Rebooting daily should be totally unnecessary for the record. That is what IT people do to mitigate problems that there are no solutions for. It absolutely should be. But when Emby acts like there's no issue you have to do what you have to do. This has worked for me so far. If I see a resolution to this issue posted somewhere I'll reconsider my approach. 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now