This update does seem to have stopped the playback errors, but the UI in the web and desktop client is still disappearing and reappearing rapidly during library scans. On MacOS, this can cause QtWebEngineProcess to crash (or at least, I have repeatedly experienced it crashing while this is happening - 4x times now).
plex_macos_ui_crash_during_rapid_refresh_from_scanning.txt (84.5 KB)
issue is definately not fixed and screen keeps refreshing
Wasnāt the fix for the playback error when screen refresh happens like during media scanning ?
It is mostly fixed, but Iāve had it happen twice today. Much less of an issue, but still an issue.
Just to be 100% clear ? What happened twice today ?
Was it, 1) Screen refresh with no playback error or 2) Screen refresh resulting with a playback error ?
Reason I ask is that I CONSTANTLY see screen refreshing when the plex server is scanning and detecting new or updated content. However, it no longer causes a playback error which is what was happening previously.
The playback error is gone, but the screen does indeed refresh occasionally when itās scanning. e.g. while youāre on the menus/home page.
Right, exactly.
Iād actually argue this is the correct behavior. For example, if Iām, refreshing metadata in the background Iād expect it to update the UI when its done that item. Also, if Iām listening to music Iād expect when that track finishes and the next one starts the recently played would auto refresh.
Anyhow, playback error fixed which is great. Plex development can decide if they want to change the screen refresh when back-end stuff changes. BTW, Iām pretty sure the refresh was always like this but maybe its a bit more aggressive now.
Iād actually argue this is the correct behavior.
New content used to pop into the library without a whole screen re-render.
Workaround
This issue does not seem to affect the Plex Home Theater Windows player, iOS app, android app, nor the Roku app in my testing. This is a valid workaround for those who only use the Web App or the Plex desktop app for Windows.
Better than rolling back or affecting my scan schedule.
It is definitely worse. At least it doesnāt interrupt playback. But I hope the refresh is still a priority for them to fix.
Anyway you could record your screen to show me what youāre seeing? You could also compare app.plex.tv to what you see on your PMS bundled web app (ip:port/web). The bundled web app is a version before the issue was introduced so it should be a good baseline to use and compare against.
Iāll be on the look out for this too. Thanks for the follow up reporting.
Just wanting to double check, on app.plex.tv, have you recently refreshed the browser or cleared cache/cookies?
Yea i have cleared cookies/cache and tested in incognito and on different pcās/browsers
see video below
Yes, this constant refreshing issue was introduced in 4.124.1 and was not been resolved in 4.125.1. It no longer breaks playback, but it makes the web app very slow and flicker constantly.
Disabling automatic library updates does reduce the issue, but this is not an acceptable workaround.
Can Plex staff please advise whether this issue can be reopened or if a new one needs to be created? It still presents a significant usability problem for users with many libraries, or with libraries that are frequently updated by automated systems. Itās difficult to use a UI thatās rapidly disappearing and reappearing under your cursor.
My concern is that this isnāt getting attention because itās marked solved. There are a number of threads around this issue and the current messaging in all of them is āthis is fixedā, but it isnāt, not completely. This thread is by far the most detailed and has the most history.
Edit: I tried switching from Plex desktop to Chromium, but the tab crashes with an āAw Snapā message during library scans.
We are still tracking this issue so thank you for continuing to report your findings.
Rolling my desktop app and server to previous version worked; before the bug, I took mine back to PM Server Version 1.32.8.7639 and desktop app to Version 1.88.1.96-c1c59fc1. No problems, since.
However, this is not a solution, just a band aid. It is baffling that this is still persistent 3+ weeks after the problems started. Iād say this needs to be reopened as I like to keep my software/server up to date
I did the same and my server is working fine too. However, I donāt see this as a solution because now our apps/servers are not up to date which may be necessary for third party plug-in, services, and/or migrations.
I didnāt find this thread until about 2 weeks in, weāre going into week 3-4. It seems the playback issue is possibly resolved, but new bugs introduced. I rolled my apps and server back to more stable releases and donāt plan to update until this is fully resolved.
Personally I like to keep my server up to date, because it can impact plug-ins, services, and/or migrating the server, which I have actually done a lot.
Wow itās really bad today. Constant refresh and when I mean constant I mean every second while itās scanning.
Personally I do and donāt recommend rolling your server and apps back to previous versions. I recommend this because you wonāt be experiencing these new, serious, and minimized by plex, bug. I donāt if need the most current version for any reason other than playback. How/why does plex staff keep marking this solved when it clearly isnāt? Maybe the playback error has been solved, but it seems new problems arose from the initial bugs.
