Issue with Firefox and transcoding

plex-web

#1

Hello.
I have an issue with the web app when using Firefox (latests version of Firefox on Mac and on Windows).

Everytime I have a user starting a video media with transcoding, the server transcode the whole file immediately. That makes my CPU burning for 3 to 20 minutes depending of the video (TV show or movies).

My issue is that most of the users I share my library with, start a show and pause it for 30 minutes and then come back at ti. Everytime my CPU transconde the whole file "for nothing".

There has been a thread on the Linux server : https://forums.plex.tv/discussion/267798/help-question-regarding-transcoding-and-firefox-insane-cpu-load

I know that this issue is not there if using Safari / Chrome (or even the plex app on ios).

Is there something I can do to have the same behavior on Firefox as on Safari (which is transcoding on the fly) ?

Thanks in advance


#2

I see the exact same issue with Opera.
Is there anybody other than me having the same transcoding issue ?


#3

This issue is known and is currently investigated.


#4

Thank you for the update :smile:


#5

Hello,
I keep having this issue. But something new : 2 days ago the transcoding issue happend with a Chrome Web browser client.
The web app used is the one on plex.tv and my server is the latest non plexpass on Ubuntu 16.04

Is there anything at all I can do on my side to help debugging this ?
Is there some cache files that I could delete or something I can do to try solving this ?


#6

Unfortunately, I have no update on this.


#7

Firefox has done this for a long time, but now all of a sudden everything has made a turn for the worse.. Chrome causes this (but not always.. I would say 50% of the time), Safari causes this 100% and even transcoding to the Plex Media Player causes this. Only time transcoder throttles is while transcoding to ATV, iOS and Android client.


#8

Yes and I don't get why there is not much threads about this.
Is it an issue some users don't have ?


#9

No idea about why Firefox has been like this for a long time, but I've found a way to replicate this every time and confirm this is now an issue with the new web player and every other browser as well.

1.

  • Login to plex.tv and use the new player.
  • Transcoder does not stop before 100% of the file is done.

2.

  • Downgrade to let's say 1.5.5 (what I did)
  • Login to plex.tv and use the new player.
  • Transcoder does not stop before 100% of the file is done, like in step 1.
  • Login directly and remotely to https://yourexternalip:port/web/index.html and use the old web player.
  • Transcoder throttles like before!

Edit: New player also produces errors like these:

[Transcoder] [mp4 @ 0416edc0] Application provided duration: -16 / timestamp: 258428904 is out of range for mov/mp4 format

No other client produce this messages, not even an older version of plexweb.

All the testing was done with the same file.


#10

So this means everybody has the issue ?
Is this a bug that the Plex team is aware of ?


#11

I've checked the logs while a player was running and the transocder not throttle.
There is some errors at the same time :
Couldn't get size of file : boost::filesystem::file_size: No such file or directory
get - invalid frameRate value: 23.976
Throttle: timed out trying to read chunk -1
[Transcoder] [Parsed_inlineass_2 @ 0x29935c0] fontselect: Using default font family: (Arial, 400, 0) -> /usr/lib/plexmediaserver/Resources/Fonts/DejaVuSans-Regular.ttf, 0, DejaVuSans[Parsed_inlineass_2 @ 0x29935c0]

Here are the server logs


#12

On Plex Pass forums, @ChuckPA told us that Plex Transcoder Team works on this issue


#13

I am currently mobile (out of office). If someone would be kind enough to quote my instructions regarding data collection for the transcoder team (debug+verbose) for web app and for bundled , I would appreciate it.

Ok, here's what we need to do. VERBOSE logs as a demonstration of what's happening. Machine not playing ANY other files for ANYONE.

  1. Set Verbose Logging & Debug Logging both ON
  2. Set transcoder pref to 60 seconds. (transcoding ahead)
  3. Stop PMS
  4. Clear all logs
  5. Start PMS
  6. Playback file for 90 seconds using bundled player
  7. Stop Playback
  8. wait 30 seconds for logs to clear
  9. Settings - Server - Help - Download Logs (capture the ZIP and set aside)

Now repeat steps 3 -> 9 for hosted Plex/web on *SAME FILE *

The Team is waiting for this.


#14

Hello,
Thank you for your time.
Here are the two logs zip asked.
The first one is when using the web/app player bundled with the plexmediaserver dpkg (using local IP)
The second one is when using plex.tv/app (using VPN to simulate outside network access)

Both playing the same file on the same browser (Firefox 55.0.2 on Mac OS X 10.12.6)

Please tell me if you need anything else.

Thanks in advance


#15

Thanks. Sent directly to the transcoder team lead.


#16

Same issue continues with Google Chrome as well, can confirm. Just started happening in the last 2-3 weeks.


#17

@ChuckPA

having these issues on all kinds of devices, mostly ROKU and Chromecast

Environment:
OS: Windows 10 Enterprise 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
GPU: Intel HD Graphics 530
Display Memory: 16231 MB
Dedicated Memory: 128 MB
Shared Memory: 16103 MB
RAM: 32GB
PMS:
PMS: Version 1.9.5.4339
Transcode quality: Auto
Segmented transcoder timeout: 20
Transcoder default duration: 30
Transcoder default throttle buffer: 180
Background transcoding x264 preset: med
Use hardware acceleration when available: ENABLED
Max simultaneous video transcode: 4


#18

@seanvree81 said:
@ChuckPA

having these issues on all kinds of devices, mostly ROKU and Chromecast

Environment:
OS: Windows 10 Enterprise 64-bit (10.0, Build 15063) (15063.rs2_release.170317-1834)
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
GPU: Intel HD Graphics 530
Display Memory: 16231 MB
Dedicated Memory: 128 MB
Shared Memory: 16103 MB
RAM: 32GB
PMS:
PMS: Version 1.9.5.4339
Transcode quality: Auto
Segmented transcoder timeout: 20
Transcoder default duration: 30
Transcoder default throttle buffer: 180
Background transcoding x264 preset: med
Use hardware acceleration when available: ENABLED
Max simultaneous video transcode: 4

please open a fresh thread as this appears to be a server issue, not a Web app issue


#19

@chu> @ChuckPA said:

please open a fresh thread as this appears to be a server issue, not a Web app issue

@ChuckPA opened here:

https://forums.plex.tv/discussion/291564/pms-error-ffmpeg-failed-to-create-direct3d-device#latest