Chris Hofmann wrote:
> The mozilla equivalent of what Netscape and a few other browser
> distributors will release in the next few weeks have been posted
> in the nightly directories.
>
> win32 ftp://ftp.mozilla.org/pub/mozilla/nightly/2001-07-25-06-0.9.2
> mac ftp://ftp.mozilla.org/pub/mozilla/nightly/2001-07-25-05-0.9.2
> linux ftp://ftp.mozilla.org/pub/mozilla/nightly/2001-07-25-04-0.9.2
>
> These builds are based on the mozilla 0.9.2 milestone with
> the addition of a collection of topcrash and other interesting
> targeted bug fixes that have been made over the course
> of the last few weeks.
>
> List of recent changes on the 0.9.2 branch are posted here.
>
>http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=MOZILLA_0_9_2_BRANCH&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=month&mindate=&maxdate=&cvsroot=%2Fcvsroot
>
>
>
> If your interested in using or playing with a very stable
> mozilla client pick one of these babies up and give it a spin.
I've been using it all day very successfully, but have just hit a very
reproduceable (for me at least) and rather deadly memory leak. It effects
both the candidate build and the trunk.
This is on our intranet, picking up pages from an IIS server using
Mozilla on NT4 (latest service pack). I'm hitting a page that causes the
progress bar to remain at the "Connecting to..." stage and seemingly
remain there. All is fine if I leave it there, the memory usage
fluctuates up and down by a few kilobytes as normal. However, if I
switch to the news client and start using that, while the progress bar
throbber is still waiting for a connection to the site, then memory
usage in NT's task manager starts growing at a rate of about 200KB/s.
Until Mozilla becomes unresponsive, followed by NT itself, and it has to
be killed using the task manager.
I can't say how easily this can be reproduced by anyone else without a
"hung" page to test against, but with this intranet example I tested it
around eight times and could reproduce it each time. The IIS server may
have been having problems, as I managed to get connection refused a few
times as well, but when it goes into that "Connecting to..." mode", this
is 100% reproduceable.
Is anything like this in bugzilla already?
ian.
--
\ /
(@_@) http://www.eclipse.co.uk/sweetdespise/ (dark literature)
/(&)\ http://www.eclipse.co.uk/sweetdespise/libertycaptions/ (art)
| |
