Our forum migration to Discourse is underway and scheduled to last through June 21. During the migration, the forums will be read-only, except for a single temporary forum (contents of which will not be getting transferred). Read our announcement post for more information about the forum migration.
Hey folks, there is a new Podcast category for forums https://forums.plex.tv/categories/podcasts
If you have not already, we suggest setting your Plex username to something else rather than email which is displayed on your posts in forum. You can change the username at https://app.plex.tv/desktop#!/account
Welcome to our forums! Please take a few moments to read through our Community Guidelines (also conveniently linked in the header at the top of each page). There, you'll find guidelines on conduct, tips on getting the help you may be searching for, and more!

Web App on Chrome runs out of sockets - buffers

_Dad__Dad_ Members, Plex Pass Posts: 17 Plex Pass

I have an issue where Chrome runs out of sockets and causes playback to buffer. Sometimes if I wait long enough playback will continue but this does not seem to be a guarantee (or I'm not patient enough).

Thoughts anyone?

Answers

  • _Dad__Dad_ Members, Plex Pass Posts: 17 Plex Pass

    Almost made it through a full movie last night without it happening. But sadly no. I did wait for it to resume which it did after several minutes. After resuming though, subtitles no longer rendered despite the client thinking they were on. I had to disable and re-enable to get them back.

  • _Dad__Dad_ Members, Plex Pass Posts: 17 Plex Pass

    No one else has seen this issue?

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass

    For what it's worth, my Plex in Chrome has been 100% fucked lately. It's constantly running out of sockets and piling up an ever increasing amount of never completing requests. No idea if something in Chrome or Plex changed recently, but I have to restart Chrome pretty much every time I need to use the web app.

  • sworcerysworcery Members, Plex Pass Posts: 1 Plex Pass

    I've been having loads of problems with plex web player ever since the most recent update. if I pause something for even a minute, and go to resume, it will stop buffering and I have to stop my stream for it to work. Funny thing is in the status page the server thinks I'm still playing the file. Other times when I go to resume playback, it will hang on loading the file and I have to refresh the page itself.

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass

    I did a bit more digging, haven't really figured out what's going on just yet.

    I am seeing really slow http://127.0.0.1:32400/player/proxy/poll?... calls being made though. Each call takes 20s usually (although I've also seen 40s), and a new call is made as soon as one finishes. It's stuck in the pending state for 20s in the meantime, so I don't know if it could be eating up sockets.

    That could be normal behavior for all I know though, and not related to the issue...

  • _Dad__Dad_ Members, Plex Pass Posts: 17 Plex Pass

    I disabled the option for Chrome to continue running in the background. This seems to have helped, but it shouldn't be an issue. I guess I will give it some time and retry later.

  • Dom CDom C Plex Employee Members, Plex Employee, Plex Pass, Plex Ninja Posts: 1,232 Plex Employee

    I'm afraid we've not seen this issue. Please keep providing any details you have though.

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass

    Does anyone else seeing this issue have access to remote shared libraries? I'm noticing some pending requests that seem to be related to getting notifications from my friend's plex server.

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass
    edited March 22

    FYI, this isn't directly related, but you can see a similar issue with running out of sockets if you just open up a bunch of Plex tabs in Chrome. You can only have a few tabs open before sockets run out and all your Plex tabs stop working. That's always been the case though, before this latest issue cropped up.

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass

    One other bit of detail, once my Chrome+Plex gets into the messed up state with the latest issue, closing all open Plex tabs and opening a new one doesn't seem to work. When you open the fresh Plex tab you'll see it stuck saying "Waiting for available socket". It's like there are still pending requests in the background, despite having closed all my open Plex tabs. Quitting Chrome completely is the only fix (or possibly if I just wait long enough).

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass
    edited March 22

    I just tried quitting my Chrome when it was stuck trying to load a new Plex tab, after letting it try for about 5 minutes. As soon as I quit, the following got dumped into my log file:

    Mar 22, 2018 12:45:03.498 [17456] DEBUG - handleStreamRead code 2: End of file
    Mar 22, 2018 12:45:03.499 [17456] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.499 [17508] DEBUG - handleStreamRead code 335544539: short read
    Mar 22, 2018 12:45:03.499 [17508] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.499 [17456] DEBUG - handleStreamRead code 335544539: short read
    Mar 22, 2018 12:45:03.499 [17456] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.499 [17508] DEBUG - handleStreamRead code 2: End of file
    Mar 22, 2018 12:45:03.499 [17508] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.499 [17456] DEBUG - handleStreamRead code 2: End of file
    Mar 22, 2018 12:45:03.499 [17456] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.499 [17456] DEBUG - handleStreamRead code 335544539: short read
    Mar 22, 2018 12:45:03.499 [17456] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.500 [17456] DEBUG - handleStreamRead code 2: End of file
    Mar 22, 2018 12:45:03.500 [17508] DEBUG - handleStreamRead code 2: End of file
    Mar 22, 2018 12:45:03.500 [17456] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.500 [17508] WARN - LongPoll: Got error, closing.
    Mar 22, 2018 12:45:03.500 [17456] DEBUG - handleStreamRead code 2: End of file
    Mar 22, 2018 12:45:03.500 [17456] WARN - LongPoll: Got error, closing.

    I then tried re-opening Chrome, accessing Plex, and then closing again. When I did that, only one LongPoll error showed up in my log file upon closing Chrome.

  • skipy10110skipy10110 Members, Plex Pass Posts: 8 Plex Pass

    Can anyone from Plex confirm if the "http://127.0.0.1:32400/player/proxy/poll?" calls taking 20 seconds to complete is normal? The response body is always empty, which seems suspicious to me.

  • Dom CDom C Plex Employee Members, Plex Employee, Plex Pass, Plex Ninja Posts: 1,232 Plex Employee

    The 20 second call to ../poll is expected, and is a deliberate long poll technique. Some platforms don't like keeping it alive for longer, so we refresh it every 20s. We use it for Plex Companion.

  • H4NDYH4NDY Members Posts: 1

    Dom C, quick question, are you / the team running Intel or AMD chips? I'm running an AMD Ryzen Thread Ripper 1950x with 16 Cores, but still have this "waiting for available socket" error as well. I know it's likely nothing to do with chipset, but you never know.

  • RumpledwarfRumpledwarf Members, Plex Pass Posts: 4 Plex Pass

    @H4NDY said:
    Dom C, quick question, are you / the team running Intel or AMD chips? I'm running an AMD Ryzen Thread Ripper 1950x with 16 Cores, but still have this "waiting for available socket" error as well. I know it's likely nothing to do with chipset, but you never know.

    Im getting this on a intel 7700k. After i pause a video plex starts buffering. I usually end up just closing the tab and opening plex in a new tab, seeing "waiting for available socket" for a while and then i can resume watching normally.

Sign In or Register to comment.