New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 748757 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Playback cannot be resumed when pausing on some HTML5 players

Reported by l...@udp.sh, Jul 25 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 OPR/46.0.2597.57

Example URL:

Steps to reproduce the problem:
1. Start playback on Plex Web App proxied by Nginx
2. Pause for an extended period
3. Attempt to resume
4. Browser throws NET::ERR_INCOMPLETE_CHUNKED_ENCODING error, playback does not resume

What is the expected behavior?
Playback resumes as normal, issue not present in FF or Opera (Based on this engine)

What went wrong?
Playback doesn't resume after an extended pause.

Did this work before? Yes 50.0.2661.75

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

Contents of chrome://gpu: 

Related issue https://bugs.chromium.org/p/chromium/issues/detail?id=622313
My attempts to work-around the issue
https://github.com/toomuchio/plex-nginx-reverseproxy/issues/21
 
Cc: hubbe@chromium.org
+hubbe@ since he's working on this code right now.
Labels: Needs-Milestone Needs-Bisect

Comment 3 by ajha@chromium.org, Jul 26 2017

Cc: ajha@chromium.org
Labels: Needs-Feedback
Could you please provide exact repro URL or Web App where media can be played to test this.

Tried https://chrome.google.com/webstore/detail/plex/fpniocchabmgenibceglhnfeimmdhdfm/related?hl=en available in Chrome Webstore but don't have any Plex Media Server to proceed with testing.
748757.png
245 KB View Download

Comment 4 by l...@udp.sh, Jul 27 2017

Ahh this gets a little tricky then.

You need to run a Plex Server then proxy it with Nginx using the configuration in the git I linked above to recreate the issue.

If it's too much of a hassle for you to do that, email me your Plex username and I'll add you to my server and you can test off that.

I'm not sure if the issue is present in the Chrome App, it probably is I've had it in the HTML5 browser version https://app.plex.tv
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 27 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: ligim...@chromium.org
Labels: TE-NeedsTriageFromMTV
Unable to triage this issue from TE end, hence adding "TE-NeedsTriageFromMTV" label
Labels: -Needs-Bisect
Removing from bisect bucket since TE cannot repro.

Comment 8 by l...@udp.sh, Aug 22 2017

A work around was found, setting the read_timeout to a high value in Nginx allows resuming playback.

https://www.digitalocean.com/community/questions/setup-nginx-to-video-streaming

Might be possible to recreate the issue without Plex following the details found in that post, this is where I found the fix.
Labels: Needs-Feedback
reporter@, can you provide a repro url in order for us to investigate this bug?
ping reporter@ again. Do you still repro this bug? if so, please provide a repro url otherwise we can't do anything.

Comment 11 by l...@udp.sh, Oct 5 2017

It is still possible to reproduce this bug I provided all the steps I can.

- Install Plex Media Server, add some content longer than 10m.
- Run it behind an Nginx reverse proxy i.e. https://github.com/toomuchio/plex-nginx-reverseproxy
- Start playback for 1m, pause for >5m, resume, network error thrown.
Not reproducible in Opera or Chrome older than 50.0.2661.75, tied to the other issue I linked above.

I found a workaround to the issue on Nginx's side by increasing the read_timeout. You can see my notes on that here.
https://github.com/toomuchio/plex-nginx-reverseproxy/issues/21

Beyond this and what I've already provided, I cannot provide anything further to assist.

If the issue isn't going to be fixed and there doesn't seem to be any interest here to investigate probably best to close this off, people can find this issue and find my work around of increasing the read_timeout. Or use Opera or an older version of Chrome without the issue.
Project Member

Comment 12 by sheriffbot@chromium.org, Oct 5 2017

Cc: yini...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "yiningc@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 13 by l...@udp.sh, Oct 5 2017

I forgot to mention but obviously remove the read_timeout workaround in the linked Nginx config, when trying to reproduce.
Components: -Internals>Media Internals>Media>Network
Owner: hubbe@chromium.org
Status: Assigned (was: Unconfirmed)
as per c#11, this issue still repro. give to hubbe@ to investigate. 
Status: WontFix (was: Assigned)
This is a server-side issue.
The server provides a streaming-only interface and then closes the connection, which cannot be resumed. Other browsers works around the issue by downloading and caching large amounts of data, which chrome intentionally does not do.

Sign in to add a comment