I'm using WMaker, and I'm not using the "no async dns" option. Whatever the
combination is, X grows in memory until it exposes hardware instabilities in
my system. X never gets that big in memory unless I run Communicator. It's
just that the odds of a crash are low when I'm not using much memory and
when I leave Communicator up for days or run multiple buildworlds I can
produce some random segfaults (processes terminate with signal 11) and
rarely a signal 4.
Doug wrote:
>
> Jeremy McMillan wrote:
> >
> > I have 128M RAM and 512M swap, and if I leave Communicator4.6 up for a long
> > period (two days?) it will take X out, and my system will reboot to boot. I
> > have issues with my CPU too, but Communicator brings out the worst in it :).
>
> Ok, you didn't mention what WM you're using. I noticed back when I ran
> afterstep that a netscape lockup would take out netscape, afterstep and X.
> With KDE the worst I have to do is occasionally kill netscape and restart
> it. Also, are you using the no async dns option? It's an environment
> variable that you set to prevent netscape from sucking up another 16M of
> ram for it's silly little DNS helper. Check out
> /usr/local/lib/netscape/README for more info.
>
> > I seriously doubt this is a STABLE issue.
>
> I agree.
>
> HTH,
>
> Doug
--
PLEASE NOTICE: THERE MAY BE NOSPAM IN THE HEADERS WHEN YOU HIT "REPLY"!!!
Jeremy McMillan <aphor at ripco.com> | Ask for PGP-2.6.2 or 5.0i
Chicago FreeBSD Users Group
http://pages.ripco.com/~aphor/ChiFUG.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
