From owner-freebsd-stable  Wed Sep  3 19:03:06 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA24781
          for stable-outgoing; Wed, 3 Sep 1997 19:03:06 -0700 (PDT)
Received: from neptune.ajc.state.net (neptune.ajc.state.net [204.120.158.168])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA24769
          for <stable@FreeBSD.ORG>; Wed, 3 Sep 1997 19:02:53 -0700 (PDT)
Received: from AJC.State.Net (saturn.ajc.state.net [204.120.158.166])
	by neptune.ajc.state.net (8.8.6/8.8.5) with ESMTP id UAA01617;
	Wed, 3 Sep 1997 20:57:45 -0500 (CDT)
Message-ID: <340E14F9.66544334@AJC.State.Net>
Date: Wed, 03 Sep 1997 20:55:05 -0500
From: Al Johnson <Al.Johnson@AJC.State.Net>
Organization: Al Johnson Consulting
X-Mailer: Mozilla 4.02 [en] (Win95; I)
MIME-Version: 1.0
To: Mike Smith <mike@smith.net.au>
CC: Khetan Gajjar <khetan@iafrica.com>, stable@FreeBSD.ORG
Subject: Re: Netscape 4.02b7 and RAM problem
References: <199709040104.KAA00512@word.smith.net.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I've been running Netscape 4.02b7 on both 2.2.2 and 3.0-970807-SNAP on a
gateway 2000 Ppro180 with 64MB of RAM without a hitch so I don't think
it's the 64MB issue.  Matter of fact I haven't had to deal with the
license-query
issue at all.

 -- Al

Mike Smith wrote:

> > I've noticed a rather curious problem. Netscape 4.02b7 worked
> > fine when my machine had 32MB of RAM in it. No problems,
> > it loaded up fine. I am referring to the FreeBSD-native version
> > of the Communicator, of course.
> >
> > Today I upgraded to 64MB of RAM, and as soon as I did, Netscape 4.02b7
> > wouldn't load unless I removed the license query in preferences.js
> >
> > Just thought you'd find this interesting. Just a increase in RAM
> > resulted in the problem(s) that everyone's discussing in both
> > this forum and hackers (there the program appears to load, but nothing
> > appears - it just takes up CPU and RAM).
>
> That's very interesting.  FWIW, this exactly matches my observations;
> on a 16M system it works fine, on a 64M system it *mostly* hangs
> requiring the license-query hack.
>
> mike