List of things to try for memory leak

[Smok@zz 4]

I, like many others are experiencing some sort of memory leak for the latest stable build of 3.2.30.0.  There is another thread that has all sorts of posts about people describing their symptoms and some solutions.  However, it is so cluttered that I was hoping people could post what they have tried and what they have seen success with until the issue is completely resolved.  I know that disabling DLNA or removing plugins are popular option but I didn't feel like I (or anyone else) should have to read through 20+ pages just to find some suggestions about what works and what doesn't.  So, for everyone that is working on this issue with Luke and team, please post what you have enabled, disabled, added, removed, or anything else you have done that you have seen success with.  Together, we can at least get our environments stable until the devs fix the code.  Also, lets not turn this thread into another troubleshooting one, this is just for things you have tried and seen positive results.  Thanks.

[SkippyJohn 8]

The only thing that has reliably worked for me is to force transcoding on the server by setting the quality level on all clients to 10Mbps.  I have tried all of the other things suggested in the other thread with no impact.  I can easily repeat memory run-aways within 35 minutes if any of my clients are set to auto quality and play direct without transcoding.  My setup is using the latest server release, hdhomerun tuner on latest firmware, windows PC clients (UWP and desktop app) and XBOX clients.  When transcoding is forced by the client setting the problems go away.  I still see memory usage on the server slowly creep up to about 1.5GB over two days and seem to stabilize there, but I do not see it simply run away and crash either the app or the entire system.

[ebr 16199]

if the reports we've seen so far are correct and the .net core version fixes this then that implies heavily that whatever this is is in the platform and not our code and, therefore, will be solved with the move to .net core.  If one of you guys can switch to that version to help verify this, that would be awesome.

[SkippyJohn 8]

I installed the .net core beta on Friday night and can confirm that from a memory consumption perspective, it seems efficient and very well behaved.  I have not been able to re-create the same memory problems that I find with the release version.  While the beta isn't ready to replace the released version for me yet, it is nice to see that this particular issue seems to be addressed with that platform.

Edited September 18, 2017 by SkippyJohn

[Luke 42086]

Thanks for the feedback.

[Happy2Play 9785]

I installed the .net core beta on Friday night and can confirm that from a memory consumption perspective, it seems efficient and very well behaved.  I have not been able to re-create the same memory problems that I find with the release version.  While the beta isn't ready to replace the released version for me yet, it is nice to see that this particular issue seems to be addressed with that platform.

 

Have you listed your issues is the Test Area?

 

https://emby.media/community/index.php?/topic/50012-emby-server-for-net-core/

[Jdiesel 1431]

It may not necessarily be bugs that need to be reported but the fact that it isn't quite ready for most people to make the change. Most people don't want to worry about migrating databases manually, doing manual updates, installing dependencies, etc. They just want to wait until the version that already have installed updates into the .NET Core version without them having to do anything.

 

I'm really looking forward to using it full time but was forced to revert back to my mono server for my production server as the lack of an image processor on Linux and some strange behaviour on my Roku's made it unusable for my family. I will continue to test myself but can see why people want to wait to switch over.

[Luke 42086]

Please try Emby Server 3.2.31. Thanks !

[SkippyJohn 8]

Tested this evening with Emby Server 3.2.32 and memory is well behaved.  Thanks!

 

Playback of live TV with Emby Theater (UWP 1.1.158 from either a PC or an XBOX) still consistently drops back to the guide at around 35 minutes.  But memory usage hold steady below 300MB the entire time, so I'll report this under the Emby Theatre section.

[Luke 42086]

Thanks for the feedback.