Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

After update Firefox now runs at 100% CPU cycles, hangs on webpage loads

  • 6 antwoorden
  • 145 hebben dit probleem
  • 3 weergaven
  • Laatste antwoord van dch4113

more options

Update Firefox to 7.0.1 version, now hangs on webpages, CPU at 100 percent usage. Disabled addons, cleared cache, reloaded version again. Still at 100%.

Update Firefox to 7.0.1 version, now hangs on webpages, CPU at 100 percent usage. Disabled addons, cleared cache, reloaded version again. Still at 100%.

Gekozen oplossing

This appears to have fixed the problem for me. Thank you!

Dit antwoord in context lezen 👍 0

Alle antwoorden (6)

more options

This is making Firefox unusable. It happens when I load multiple pages at once, or when I load single pages for some websites (specifically articles at www.techrepublic.com). CPU usage goes to 100% and stays there until I restart Firefox. Sometimes a part of the page will load (I get the title), and sometimes it just says "Connecting".

Just started happening recently, so I'm assuming it has something to do with version 7.0.1. And I am also running WinXP. The behavior is similar to what you'd get if you had some sort of infinite loop.

more options

More info: I downgraded to version 7.0 and still had the problem, so it's not just a 7.0.1 issue.

more options

Downgraded to version 6.0.2, and the problem went away.

more options

The default of the pref network.http.max-connections has been increased from 30 to 256 in Firefox 6+ versions.

Try to decrease the value of the pref network.http.max-connections from 256 to 30 as used in Firefox 3 versions.

more options

Gekozen oplossing

This appears to have fixed the problem for me. Thank you!

more options

Good call on the fix. Problem was clearly setting was too large for older generation desktop. Thanx.