Platform - Windows 10 PC
Plex Media Player - 1.25.5.5492
Chrome Version - 98.0.4758.102
Started happening to me this morning, video will play for a 90-120 seconds then it freezes up.
Had no issues before Chrome updated to ver.98 but the problem also persists in Edge (gotta be desperate for me to load Edge up)…
This is very frustrating and has rendered your service unuseable on my desktop…which is where I consume most media.
Chrome was updated this morning & so far seems to be back to normal
This started happening today, coincidentally (apparently) as I added some FLAC albums to Plex that I’ve been listening to today.
Just updated Chrome to Version 98.0.4758.102 (Official Build) (arm64), but same crash.
The Plex desktop app works well.
Looks like it’s working for me as well…
Updated to Chrome Version 98.0.4758.102 (MacOS).
While it did seem to be more stable for a bit, the issue just cropped back up with the same symptoms as before.
Yep, crashing again in Chrome. Reloading the page 3 times sorted it, not ideal
Opera now doesn’t even open the page, but was working yesterday
I had a separate post about this, but I’m adding it here and deleting my post…
There are some songs in my music collection that when I try to play them I get a messages saying “Awww, Snap! Error 5” in Chrome Version 98.0.4758.102 (Official Build) (x86_64) on a Macbook Pro running Big Sur.
The only happens when I go through app.plex.tv, and not when I go directly to my server or using the Mac app.
An example, I have an album that I purchased on Bandcamp, unzipped the zip file I downloaded and it now shows in Plex. If I try to play the first song (using app.plex.tv to connect), it crashes wit the error. If I try to play the 2nd song, it crashes with the error. When I try to play the 3rd song, it works (and the rest work).
It’s not ONLY these two songs, although I don’t remember off the top of my head.
When it happens, I’ll see on the dashboard that I’m playing the songs that crashed even though they’re not playing. So if I try to play the first song 5 times and it crashes each time, it will show up 5 times as “Now Playing”
Same issue here
Hi bengeorge,
I experienced the problem mainly when pausing songs then hitting play, clicking on the time bar, or closing the browser on a paused song then trying to resume it after reopening the browser, only on chromium browers (Firefox seems unaffected).
There are two workarounds that I am aware of :
The are some interesting console logs here : Plex Server crashing after google chrome update 98.0.4758.81(Official Build) (64 bit) - #29 by TurboMyPC
I’m not sure but I think the problem could come from an “OPTIONS” request not properly handled by Plex server. See this page : Chrome Enterprise release notes - Chrome Enterprise and Education Help, “Private network access preflights for subresources” section :
Chrome sends a CORS preflight request ahead of any private network requests for subresources, asking for explicit permission from the target server. This request carries a new Access-Control-Request-Private-Network: true header, and the response must carry a matching Access-Control-Allow-Private-Network: true header.
I’ve seen everybody say that Firefox works fine, but I just encountered something very similar just now:
It’s been weeks since this has been happening. Is there really no word yet from any Plex devs…? 
last official comms looked like they were having difficulty producing the error.
i’m on chromebook, latest plex and chrome os. I get it on ‘most’ videos. Some need to play longer than others for it to crash out. Sometimes 10-15+ minutes. I tried to compare ones that worked vs those that don’t. There wasn’t a noticeable significant different between files/codec/bitrate, etc to determine if that has anything to do with it.
the problem for me is for movies/videos in plex web (latest). I’ve not tested audio tracks.
Hi all,
Is it just me or is the issue fixed?
Updated Brave yesterday and now the movies that were crashing the browser are working. So I guess so 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
