Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Learn More

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

Since upgrading to 3.6.10 it appears that there is a memory leak. The browser becomes unuseable until I shut it down and restart. I have tried bookmarking my tabs in the 6 windows which I generally run but ... Any ideas on how to trouble shoot? Thanks

  • 2 odgovora
  • 75 ima to težavo
  • 1 ogled
  • Zadnji odgovor od mig

mig
mig
more options

Firefox 3.6.10 under Mac OS X 10.6.4 with a Mac Pro (Tower of Power) 2 - 3.0 GHz dual core Xeons, 5 GB RAM. Firefox takes up to 1 GB of memory and CPU usage goes over 100% in the Activity Monitor.

Firefox 3.6.10 under Mac OS X 10.6.4 with a Mac Pro (Tower of Power) 2 - 3.0 GHz dual core Xeons, 5 GB RAM. Firefox takes up to 1 GB of memory and CPU usage goes over 100% in the Activity Monitor.

Vsi odgovori (2)

mig
mig Lastnik vprašanja
more options

I've recently downloaded 4.0 beta. Works much better than the patched 3.6.10 which becomes unusable. I have loaded up the 4.0 Beta browser with the same number of Windows and Tabs which could reproduce the original problem. Viewing under the Mac OS Activity Monitor while there might still be a memory leak, I believe that the largest problem seems to be a thread that has taken over the CPU(s) and not relinquishing control. When the problem would occur the CPU Usage would go over 100% with the 4.0 Beta it is only at 12%. Memory usage ranges from over 1 GB with 3.6.10 to 650 MB with the 4.0 Beta. I did clear out my download list and the browsing content could account for the differences in memory usage. Hope that this helps.

-- mig

mig
mig Lastnik vprašanja
more options

I believe that this issue has been resolved by upgrading the Adobe flash plugin to version 10.1.85.3.