Commentary

Mitch Wagner
Executive Editor, Community  

Mozilla Fixes Memory And CPU Problems In Firefox 3 Beta 1

Mozilla.org says it fixed a problem with Firefox 3 Beta 1 that caused it to spike CPU usage and eat hundreds of megabytes of RAM. The fix involved changing the configuration of a server that Firefox communicates with, so you don't have to download a new version to take advantage of it.

Mozilla.org says it fixed a problem with Firefox 3 Beta 1 that caused it to spike CPU usage and eat hundreds of megabytes of RAM. The fix involved changing the configuration of a server that Firefox communicates with, so you don't have to download a new version to take advantage of it.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The bug affects Firefox installations with very outdated lists of bad sites for the phishing protection and malware protection features of the browser, according to a report on Mozillazine.. It also affects installations that have no list of bad sites at all. "Firefox is trying to bring down these rather large lists in one big chunk rather than slowly in small chunks. This causes Firefox to consume large amounts of CPU and memory and can slow the users machine to a crawl," according to the blog author, Asa Dotzler, community coordinator of Firefox marketing projects.

Dotzler said he thinks that was the cause of a problem I encountered running Firefox 3 Beta 1 on a five-year-old Compaq laptop, where Firefox 3 B1 ran so slowly as to be useless, even though Firefox 2 runs fine. I haven't tested it out on that machine to see if the problem is, indeed fixed. I've been using Firefox 3 B1 as my production browser since I installed it Wednesday, the day it became available, and I've found it to be very stable, even though others have reported problems.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links