Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Need help with strange crashing problem

  • 3 odgovora
  • 9 ima ovaj problem
  • 11 prikaza
  • Posljednji odgovor od Jacob Bruce

Jacob Bruce
Jacob Bruce
more options

Hi guys,

I'm using Firefox 14.0.1 on Windows 7 32 bit. The problem is that every few minutes my browser crashes. The memory usage appears to rise and rise until it reaches a point where it causes Firefox to crash.

In safe-mode the problem doesn't occur. So naturally I tried disabling all my add-ons to re-enable them one by one and attempt to locate the offending add-on. This is where it gets strange.

After I disabled all my add-ons and even all the plugins, the problem was still persisting. So Firefox is working in safe-mode but out of safe-mode with all my add-ons disabled the problem still occurs.

So at this point I'm really not sure what do to. I assume safe-mode is doing something which I haven't yet thought of doing, but I'm not sure what. Any help with the problem will be very much appreciated.

Cheers.

Hi guys, I'm using Firefox 14.0.1 on Windows 7 32 bit. The problem is that every few minutes my browser crashes. The memory usage appears to rise and rise until it reaches a point where it causes Firefox to crash. In safe-mode the problem doesn't occur. So naturally I tried disabling all my add-ons to re-enable them one by one and attempt to locate the offending add-on. This is where it gets strange. After I disabled all my add-ons and even all the plugins, the problem was still persisting. So Firefox is working in safe-mode but out of safe-mode with all my add-ons disabled the problem still occurs. So at this point I'm really not sure what do to. I assume safe-mode is doing something which I haven't yet thought of doing, but I'm not sure what. Any help with the problem will be very much appreciated. Cheers.

Izmjenjeno od Jacob Bruce

Izabrano rješenje

Ok, yes the problem is being caused by the hardware acceleration. My browser is working fine now that it is disabled. Apparently this has something to do with the newest AMD video drivers:

https://support.mozilla.org/en-US/questions/927206

I recently upgraded to the newest drivers and now I'm getting this problem. I suspected it had something to do with it. Apparently these problems have been happening since FF 12. This really needs to be sorted out.

I will just use FF without hardware acceleration for now, but I hope we can see a fix for this in the next release. Or if it's actually a problem with the AMD drivers then hopefully they will get into it. Either way it needs a fix.

Pročitaj ovaj odgovor u kontekstu 👍 2

Svi odgovori (3)

user66338
user66338
more options

Hey,

can you please create a new Firefox profile, by following the steps mentioned here: Creating a profile

After that, you can reinstall all your add-ons and see if the issue persists.

--Tobbi

ideato
ideato
more options

Try to Turn off hardware acceleration and check it again (in safe mode Hardware acceleration is disabled).


thank you

Jacob Bruce
Jacob Bruce Vlasnik pitanja
more options

Odabrano rješenje

Ok, yes the problem is being caused by the hardware acceleration. My browser is working fine now that it is disabled. Apparently this has something to do with the newest AMD video drivers:

https://support.mozilla.org/en-US/questions/927206

I recently upgraded to the newest drivers and now I'm getting this problem. I suspected it had something to do with it. Apparently these problems have been happening since FF 12. This really needs to be sorted out.

I will just use FF without hardware acceleration for now, but I hope we can see a fix for this in the next release. Or if it's actually a problem with the AMD drivers then hopefully they will get into it. Either way it needs a fix.