Firefox 144.0 (aarch64) on mac desktop is bricked when trying to get into gmail acct.
Firefox 144.0 (aarch64) on mac desktop is bricked when trying to get into gmail acct.
Firefox 144.0 (aarch64) on mac desktop is bricked when trying to get into gmail acct.
This morning, Firefox updated automatically to Firefox 144. However, this update completely broke Firefox; every tab crashed, and I couldn't even use Firefox to get to t… (läs mer)
This morning, Firefox updated automatically to Firefox 144. However, this update completely broke Firefox; every tab crashed, and I couldn't even use Firefox to get to this help site.
Edition Windows 10 Enterprise Version 22H2 Installed on 03/25/2022 OS Build 19045.6332
Changing my OS is not an option for me; those decisions are made far, far away. I was allowed to use Firefox instead of Chrome. Sadly, I have to switch over to Chrome today in order to work. :(
I have added a couple of screenshots.
I am moving over to Chrome to do some work.
Thanks for any help, B
Using Windows 10, Norton 360, Roboform, Firefox 143.0.4, PC Manager on Boost. Tabs keep crashing and do not know why. Is this being fixed?
Firefox repeatedly crashes on my, multiple times a day. I'dc really like to NOT have to change my default browser to Chrome. What happens is that Firefox freezes, and I… (läs mer)
Firefox repeatedly crashes on my, multiple times a day. I'dc really like to NOT have to change my default browser to Chrome.
What happens is that Firefox freezes, and I get a white bar at the top telling me so. I get a popup box asking if I want to close Firefox or wait for it to respond. Waiting doesn't work, so I always have to close Firefox. When I reopen it, fortunately all m,y open tabs are retained, but it crashes again within minutes or seconds as soon as I click on anything.
There only thing that seems to work is a reboot of my PC. But the respite is short before Firefox crashes again.
I've disabled most plugins, but that hasn't helped. Is there a way to create an event log within Firefox that I can share with someone at Mozilla to help e debug the issue? It's got to be something local rather than Firefox itself; I can't imagine this is happening to most users.