Transcoder issues when seeking - gets to 100% CPU

[bitpushr]

@sa2000

I can see you shutting down Plex Media Server a number of times

Yes, that was from me having to manually re-start Plex after duplicate Transcoder threads were started. It’s either that or have the VM crash from 100% CPU use.

@sa2000

Seeks are done by killing the existing transcoder process and starting a new one - that is how it is done.

It would appear, then, that instead of doing that, Plex is simply starting a new one without killing the existing one. I should also note that after the duplicate transcode thread is started, Plex just buffers and refuses to play on the client.

@sa2000

I will move your post and my reply to a separate new forum topic as it is not related to this forum thread which is for the Plex Media Server.exe process crashing

No problem, apologies for the post in the wrong area.

@sa2000

Having looked at your logs, I can see an issue with how seeks are being handled leading to repeated transcoder processes being started for same seek.

That’s good to know!

@sa2000

we may need the file that exhibited this issue to reproduce the problem

You can access the file here, you will have to download it:
https://drive.google.com/open?id=1IqAo6KYg4EaijEFYsGqrF7ViPOVSEVja
I should note that I’m able to reproduce it across a number of TV shows across varying file formats, predominantly mkv and mp4.

@sa2000

Does the problem arise with any seek ?

Yes, if the client requires transcoding I’m able to reproduce it 100% of the time.

@sa2000

Does the problem also arise with media on a local drive ?

Correct.

@sa2000

Could you let me have the media info xml for that library item

xml.txt (2.7 KB)
Here are some manual screenshots I took of the media info as well:

I can also confirm, after rolling back to Plex version 1.18.0.1944 I’m as yet unable to reproduce the issue, though I’m waiting on my remote client who uses his Xbox One to confirm the issue is gone for him.