[conspire] (forw) Re: Firefox & Windows 7 Memory Leak.

Rick Moen rick at linuxmafia.com
Sun Sep 11 12:44:11 PDT 2011

----- Forwarded message from Rick Moen <rick at linuxmafia.com> -----

Date: Sun, 11 Sep 2011 12:43:02 -0700
From: Rick Moen <rick at linuxmafia.com>
To: Jesse Monroy <jesse650 at gmail.com>
Cc: John Sokol <john.sokol at gmail.com>, b c <crawford.bill at gmail.com>
Subject: Re: Firefox & Windows 7 Memory Leak.
Organization: If you lived here, you'd be $HOME already.

Quoting Jesse Monroy (jesse650 at gmail.com):

> As you can see, this problem is reported on Mozilla's own websites,
> and the person reporting the issue seems to have good knowledge
> about computers. No doubt these issue arise with new browsers,
> CSS, Adobe flash and other so-called modern advancements in
> web-browsing.
> http://support.mozilla.com/en-US/questions/753700?s=egg&as=s

While the question with all Netscape and Mozilla Web browsers has never
been _whether_ they leak memory but rather just at what rate, the smart
money would be on one of the classic problem-child proprietary
extensions, and the #1 logical suspect is always Adobe Flash.

Both the Google Chromium/Chrome browser and the Apple Safari one run
browser extensions in their own separate processes, such that Adobe
Flash doesn't take the whole browser down when it bombs out of memory.

Within the browser itself -- any Web browser -- the portion of the
codebase most likely to generate memory leaks is the JavaScript engine,
typically a nasty piece of work exposed to horribly malformed input from
public code.  This is one of the many, many reasons why the best thing
you can do for browser _performance and reliability_ (in addition to
privacy and security) is to run with NoScript enabled.

----- End forwarded message -----

More information about the conspire mailing list