Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.
Resources (JS, images, etc) only partially load unless bypassing cache after Firefox v100.0.2 update?
When I load a page the first time, everything loads normally. Then if I refresh the page with CTRL-R, resources on the page (such as .js files) very often (seemingly 75% of the time) only partially load and therefore parse errors occur in the console. To reload a page, I have to hit CTRL-SHIFT-R to bypass cache and then the page loads normally again. I can also just launch the page in a private window (this loads properly), close the window and launch it again in another private window (this loads perfectly still) but it's becoming a chore to juggle with private windows only to reload a page I'm working on. I can see the resources loaded under the NETWORK tab in the console but they don't seem to be available to the page renderer or something.
Is this a bug in v100.0.2 or was I only having a bad weekend and all of this is just a random glitch that will go away soon? I've never had a problem like this with any previous Firefox releases (even v100.0) and I've used FF for approximately 15 years. It immediately began to happen after the v100.0.2 update!
What I have done so far:
- Exit out of Firefox and launch it again. - Rebooted the computer. - Site Information > Clear Cookies & Site Data - Waited 2 days for another FF release in case this was a bug and it rapidly got fixed (no update rolled out since). - Help > More Troubleshooting Information > Clear Startup Cache
Am I going crazy or?
Well, I'm an idiot. Turns out my C: drive was 99% full and 75% of the time this was too much full for Firefox to properly store its cache, it seems. I cleaned useless files and now that the C: drive is less full, it didn't do it all day, so I think it's resolved. Sorry, I'm an idiot! :PRead this answer in context 👍 0
All Replies (1)
Well, I'm an idiot. Turns out my C: drive was 99% full and 75% of the time this was too much full for Firefox to properly store its cache, it seems. I cleaned useless files and now that the C: drive is less full, it didn't do it all day, so I think it's resolved. Sorry, I'm an idiot! :P