Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.
FF 15.0.1 repeatedly freezes my entire computer; can't forcequit; need power button to shut down/restart; completely random, not an addon issue.
This is a freeze, not a crash, so I can't submit info to Mozilla. I've been through this in repeated updates, and it's only getting worse. FF used to be stable, now it's unreliable. I have OS X 10.6.8, fully updated. I have only 2 add-ons: Jave Applet Plug-in 13.8.3 and Shockwave Flash 11.4.402.265. It's entirely random, and usually with an ordinary site, with no video or pop-ups or anything moving. Force-quitting doesn't work; FF shows it's closed in the dock but the window is still open on the screen, and the beachball is spinning. It progressively freezes each app I click on, and finally I have to use the power button to shut down and restart. Again, this is getting worse, not better. I moved to FF because IE and Safari were so bad, but now FF is no better. Thankfully Word seems to save whatever I'm working on if I have to shut down, but email doesn't. With this kind of freeze, I'm not given the option to submit info to Mozilla - everything is frozen, the submit window doesn't even appear.
All Replies (10)
Does that happen when the computer goes to sleep, then wakes up? I have an issue with Firefox locking everything up on my computer when it wakes up. I make a point of exiting Firefox before leaving the computer for more than a few minutes.
No - because my computer never sleeps; it's always running calculations in the background, so it's awake 24/7.
My FF 15.01 keeps freezing as well.
Come on guys, this forum is FULL of people with this issue.
You've already lost countless users to Chrome. Do you want to lose more?
I spent many years on OSX 10.4 using FF with little problem. It was a bit bloated but worked fine.
Once I got a new machine and went to 10.6, my FF experience went downhill fast. I'm now on 10.6.8 and FF15 and it's by far the worst experience I've ever had with a browser.
It is, frankly, abysmal.
In the course of a typical working day, I estimate I have to force quit FF around 40 - 50 times. If I start or quit any other app, FF locks up shortly after.
I was having the same problem.... But I keep forgetting that when you upgrade firefox... or it updates automatically... you need to right click on the firefox start up icon, go into properties, click on the compatibilities tab, and put a check in the "Run This Program As An Administrator" box, then hit apply. Start Firefox, and it should work OK. Problem is...each time you upgrade firefox and/or I think Adobe flash... you need to make sure that box is checked. This is on Firefox 15.0.1 with Adobe Flash 11.4.402.278 all up to date, Windows 7 64bit.
Checking your username for previous posts (here) I see that you also posted the same information in a number of other threads today.
You don't normally need to check the "Run This Program As An Administrator" box in Firefox -> Properties -> Compatibility tab after an updating Firefox or Flash. If you need help with this issue, you should ask a new question. You can use this link as a starting point: https://support.mozilla.org/questions/new
Okulungisiwe ngu AliceWyman
Why should he ask a new question? It's already been asked, here and elsewhere.
This thread was started by roughbeast, who is a Mac OS X 10.6 user who is having problems with Firefox freezing the entire computer. cutmetal's answer was for a Windows 7 problem and his solution wouldn't work on Mac OS.
roughbeast, Getting back you your original question, see Firefox hangs or is not responding - How to fix and this article for possible solutions:
.... but if the entire computer is locking up and you are having the same issues with Safari then your best bet might be Apple Support.
My apologes. In my rush for a solution, I didn't even check that. My issue is with w7, latest FF.
CUTMETAL is right!
"Run This Program As An Administrator" seems to have stopped my slow, plodding, sluggish FF 17 problems for the last few days! I was just about to ditch for Chrome before hitting this page.
try his solution. Cheers CutMetalL