Server Crashes and atleast 9 PlexTranscoder.exe running in Task Manager for just one streamer

Server Version#: 1.13.8.5395
Player Version#: (Don’t Know - Latest XboxOne version available)

This has happened twice in the last week. I have one remote user streaming, perhaps a few movies in a row, but obviously only one movie at a time, and eventually it stops responding, when I look at the server during this time I see about 9-10 maybe more PlexTranscoder.exe instances running in Task Manager. If I attempt to access the server 127.0.0.1 as usual, it will not respond. I have to kill each PlexTranscoder.exe instance, kill the server and then relaunch it in order for everything to return to normal.

The server is Windows 10 Pro Virtual machine with 8 GB of RAM running AMD Threadripper 1950x.
For what it is worth, the first time it happened, the same Xbox user was streaming remotely, a second remote user was streaming from a Samsung TV, and I was direct playing locally from Nvidia Shield; mine was the only connection that kept streaming, even while the server was unresponsive from web interface.

Please run with debug logging enabled
Restart the server

when you get the failure to get to the server via 127.0.0.1:32400/web restart and get the logs

see
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/

Thank you for your help sa2000. Logs had already been enabled; I’ve attached them. The issue seems to have happened somewhere between 19:00 and 19:35 on 10/18/18.

Any help would be appreciated.

Plex Media Server Logs_2018-10-19_06-49-40.zip (3.1 MB)

Happened again last night. The only correlation I have is that it keeps happening when the Xbox user is streaming. He has the latest plex player for Xbox One.

I had an initial look and we were doing a lot of skips backwards and forwards and each would result in a new transcoder job being created - the other one should get closed down and terminate though.

I have not yet established if the skipping back/forth is genuine or is to do with network speed and packets for a stream getting there faster than other stream and requests for packet numbers become non continuous making it appear as a skip.

I will come back to you once i looked into the logs.

Hi. Any update on this?

Thanks.

I don’t have any update on this. But there does appear to be a timing issue in Plex Media Server when dealing with skips as each skip ends with the transcoder process being killed off and a new one started - Try and avoid skipping forward / back when streaming - whilst the issue remains outstanding

I should have mentioned that the problem has already been referred to our development team

Thank you for your help.

The beta version released this week - Plex Media Server 1.14.0.5468 addresses the deadlocks that arose when there werre a lot of seeks which was what was happening here - please update and let me know with fresh evidence what the outcome is. Any multiple transcoder jobs started should get closed down anyway

Details:

Plex Media Server 1.14.0.5468 has just been released as Beta. It has a fix for the deadlock seen in diagnostics provided in this forum thread.

See Release Notice

  • (Transcoder) Resolved a rare deadlock (#9332)

Thank you for your work on this issue. I will let you know if I see the deadlock again.

Thanks.

just checking up on loose ends - @adamtaguirre - what is the position with this? Have the changes to address the deadlock cleared the other related symptoms

Thanks for following up. I guess the good news is that I/we haven’t experienced that problem since. However, the user hasn’t streamed from their xbox since then either. So I can’t definitively say the issue is fixed. IF it happens again in the future, I will post about it, but you can consider this issue resolved for now.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.