memory usage in firefox and gecko
For a long time there have been a lot of complaints about the memory usage in Firefox and anything else that used the Gecko engine. And looking at the numbers for what Firefox would use for memory, they seemed valid. But on the other side of the story …
Context & Ripple Effects
The memory complaint is old news by November 2007 — but September brought a shift in how it was handled. Jesse Ruderman's leak roundup catalogued the outstanding bugs, while Berlind argued that Gecko's open source base means any developer can add fingers to the "leaky dam" rather than waiting on a vendor patch cycle. Christopher Blizzard's post now supplies the counterweight: he accepts that the raw numbers look valid but insists there is another side to what they measure — the perennial question of whether cached allocations count as leakage.
The stakes are competitive, not cosmetic. By January 2007 Firefox held a confirmed 14% U.S. share and had grown for three straight months while Microsoft lost ground despite 100M IE7 installs — an erosion dating back to at least December 2005. A browser winning converts on speed and trust cannot let a "memory hog" reputation harden, which is why a Mozilla insider engaging the numbers directly matters more than the bug reports themselves.
First-order effects
- Blizzard's argument forces the leak conversation onto measurement ground: if caches and allocator behavior explain part of the reported footprint, the September bug roundups and the dam-plugging volunteer effort are attacking a smaller problem than headline numbers imply.
- Mozilla's credibility is directly on the line — an insider disputing the framing of user complaints risks the same backlash the complaints created, unless the alternative accounting persuades the developers already working the leak list.
Second-order effects
- Rivals benefit without doing anything: Internet Explorer's marketing problem is relative, so every month the Gecko memory narrative stays unresolved slows exactly the switching flow that has been eroding Microsoft's dominance since 2005.
- How memory is measured becomes contested territory — third-party tests and blog benchmarks gain agenda-setting power over browser perception, pressuring both Mozilla and Microsoft to publish their own numbers.
Third-order effects
- If the pattern holds, browser competition consolidates around verifiable resource footprints as a ranking axis alongside standards support and security — making memory accounting methodology a durable part of how engines like Gecko are judged.
- Sustained public pressure on memory behavior points toward allocation and caching strategy becoming an explicit engineering discipline inside browser projects rather than an emergent side effect.
The trend: With Firefox taking share from IE on trust and speed, browser competition is expanding to include memory footprint and whose measurement of it the market believes.