cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Latest update QC is bad

Core279
Making moves

So recently I finally updated to Firefox version 132 because the update reminder pop up coming back repeatedly after dismissing it got annoying. I had Firefox set to open on PC startup and update 132 would make my PC bluescreen shortly after startup. The fix was making Firefox NOT open on startup. The only way I could actually change the setting and have it stick was to use a Windows restore point from before the update.

However, there is still another sizable issue. The latest update does NOT agree with YouTube. The navigation sidebar is missing, videos have to load the page twice to get a video to be playable, shorts only show the same ones that I can count on one hand, comments are missing everywhere, and my recommended videos page only gives me about one page's worth before not having any videos displayed to be selected at all.

I have tried disabling all my add-ons, disabling even my antivirus, fiddling with various settings, and nothing works. The ONLY thing that works is clearing YouTube's cache completely, which makes me have to log in again, and even then it only works for the main page for one session. Once I close YouTube's tab and come back later, the issues are back in full swing again.

None of these things(YouTube's various issues, and Firefox opening on startup causing a hard PC crash) were an issue until I installed version 132. Something needs to be addressed with internal QC, as the only third-party things that have been added to Firefox are from my Antivirus(Avast) and from Nvidia. and I am running the latest drivers. I've even tested in other browsers and don't have these issues. Until the next full Firefox update releases in a non-beta fashion, I will be reverting back to v131 and just deal with the reminder popup, instead of a broken major website and startup crashes.

1 REPLY 1

judydayisbell
Making moves

I'm having the same issues with version 132.0.1. Has anybody found a solution to this? Is Mozilla looking to send out a patch?