<OT> Re: Mozilla memory leak

[Tim Wunder]

On 5/31/2002 10:50 AM, someone claiming to be Net Llama! wrote:
<snip>

> 
> I'm just skeptical, as if this problem was as evident as others claim, it
> would be far better known by now, especially as we approach the 1.0
> release.
> 


Very close. In fact, what's available now from http://ftp.mozilla.org/pub/mozilla/nightly/latest-1.0.0/ is very likely to *be* 1.0, at least according to a post on netscape.public.mozilla.seamonkey:

<quote>
> The MOZILLA_1_0_RELEASE branch has been cut and while
> there is some tiny chance that we will need to take
> further changes, it is highly probable that this is
> the source we will release as Mozilla 1.0.
> 
> Binaries created from this tag will live here:
> http://ftp.mozilla.org/pub/mozilla/nightly/latest-1.0/
> Try them out.
> 
> Note that these are just test builds. Mozilla 1.0 has not
> been released yet. If you look at the user agent or
> the about: page you'll see a browser that claims to be
> Mozilla 1.0, but don't be fooled.
> 
> 
> Here are the directions for pulling the source from the
> Mozilla 1.0 release tag.
> 
> On Unix:
>    cvs co -r MOZILLA_1_0_RELEASE mozilla/client.mk
>    cd mozilla
>    gmake -f client.mk checkout
> 
> On Win32:
>    cvs co -r MOZILLA_1_0_RELEASE mozilla/client.mak
>    cd mozilla
>    nmake -f client.mak pull_all
> 
> On MacOS:
>    In MacCVS Pro, open your Mozilla session, then choose the
>     "Action / checkout other module to..." menu item and fill out:
>      module: mozilla/build/mac/build_scripts
>      Check out to: MOZILLA_1_0_RELEASE
>    Then run 'BuildMozilla{Debug}.pl' as usual
> 
> 
> 
> 
> If you're on a platform besides windows, Mac OS 9, Mac OS X,
> Linux or FreeBSD, then your platform may be affected by bug
> 147333. (Cannot load local files whose names contain
> non-ascii characters)
> http://bugzilla.mozilla.org/show_bug.cgi?id=147333
> 
> If you're affected by this bug then please help by
> by testing patches and giving feedback. (the fix is
> still in progress)
> 
> The patch for this bug probably will not go in to the
> final 1.0 release, but we're hoping a patch will be
> ready soon so that people on broken platforms can apply
> it to the normal 1.0 tree and release the patched bits
> instead. Watch the bug for more details.

</quote>

Tim