Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше
Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.
Вирішено Архівовано

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

dch4113 відповів
dch4113

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%.
Читати цю відповідь у контексті

Вибране рішення

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

Усі відповіді (6)

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 info: I downgraded to version 7.0 and still had the problem, so it's not just a 7.0.1 issue.

Downgraded to version 6.0.2, and the problem went away.

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.

Вибране рішення

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

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