After upgrade to, Plex Transcoder now randomly starting lots of threads



Which sends my system load through the roof (over 30). I can't see any rhyme or reason to why/how these transcoding threads are started. No-one is watching any content through any client apps. Here's an example process list:

plex 5821 2032 66 20:32 ? 00:08:54 /usr/lib/plexmediaserver/Plex Transcoder -codec:0 hevc -ss 120 -i /media/video/TV/Westworld/Season 2/Westworld - S02E04 - The Riddle of the Sphinx - HDTV-1080p.mkv -map_inlineass 0:2 -filter_complex [0:0]scale=w=1920:h=1080[0];[0]format=pix_fmts=yuv420p|nv12[1];[1]inlineass=font_scale=1.000000:font_path=/usr/lib/plexmediaserver/Resources/Fonts/DejaVuSans-Regular.ttf:fontconfig_file=/usr/lib/plexmediaserver/Resources/fonts.conf[2] -map [2] -metadata:s:0 language=eng -codec:0 libx264 -crf:0 16 -maxrate:0 14332k -bufsize:0 28664k -r:0 23.975999999999999 -preset:0 veryfast -x264opts:0 subme=0:me_range=4:rc_lookahead=10:me=dia:no_chroma_me:8x8dct=0:partitions=none -map 0:1 -metadata:s:1 language=eng -codec:1 copy -copypriorss:1 0 -f segment -segment_format matroska -segment_format_options live=1 -segment_time 1 -segment_header_filename header -segment_start_number 0 -segment_list -segment_list_type csv -segment_list_size 2147483647 -segment_list_separate_stream_times 1 -avoid_negative_ts disabled -map_metadata -1 -map_chapters -1 chunk-%05d -map 0:2 -f null -codec ass nullfile -start_at_zero -copyts -y -nostats -loglevel quiet -loglevel_plex error -progressurl

Last time this happened about a dozen separate processes were started up. They run for a few minutes then go away. This has never happened before . I do have thumbnail generation on, but that only runs during the scheduled tasks window.

My system is running Ubuntu 16.04.4, fully patched and updated.


Please post the full logs so that we can tell you which user / client started the transcode session.


After checking the PMS logs, I’ve determined that a rogue client is the cause–the Plex add-on for Kodi Krypton. Restarting Kodi didn’t do the trick, so I rebooted the whole Kodi box and the issue appears to be resolved. Not to say that it won’t reoccur.