Various ServerApplication Errors with 3.2.20.0

[y2kse 5]

A few days after upgrading from 3.2.10.0 to 3.2.19.0, Emby became non-responsive on client devices.  When I checked my server, I noticed that Emby had consumed nearly all available memory, the transcoding-temp folder was consuming > 150 GB of space and the server logs were massive (one I still have is 432 MB).  Rolling back to 3.2.10.0 resolved the issues.  The problems returned after upgrading to 3.2.20.0 and rolling back to 3.2.10.0 again resolved them.  

 

I've attached server logs from the past several days.  The devices with IP addresses 192.168.1.55 and 192.168.1.172 are Roku 3 and Roku 2 units.  I am not aware of playback issues on the Roku 3 and did not experience any on the Roku 2.  There weren't any errors logged in the remux and transcode logs.  There are also no errors logged in Windows Event Logs.

server-63633151483.txt

server-63633281851.txt

server-63633318803.txt

server-63633319706.txt

server-63633340800.txt

server-63633427202.txt

Edited June 19, 2017 by y2kse

[Luke 42080]

I think we are being too aggressive trying to send the roku app realtime updates. We'll tone that down for the next server release, thanks.

[y2kse 5]

Thanks.  I'll keep an eye out for a new release.