From owner-freebsd-current Mon Feb 21 23:12:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 8435D37B590 for ; Mon, 21 Feb 2000 23:12:34 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA10826; Tue, 22 Feb 2000 02:11:59 -0500 Date: Tue, 22 Feb 2000 02:11:59 -0500 (EST) From: Mike Nowlin To: Kenneth Wayne Culver Cc: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: Crashing netscape? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You may want to try upgrading your linux libraries... they may be old... I > don't have these problems though... Netscape rarely crashes for me. Me and one of my friends got really sick of this problem one weekend a few months ago (under Linux), and decided to figure out what was blowing up... After trying LOTS (about 40) of different library versions in even more (several hundred) combinations, we finally found a few combinations that worked (basically) every time... NS would still blow up when heavily strained, but 99.9% of the time it worked fine... This was on Slackware and Redhat Linux, dunno which versions.... (It really doesn't make any difference.) The general rule that we found is to take the NS version you're running, do an "ldd" on it to get the required libs, and go find what was at the time of that NS version release the most recent version of each library. Upgrading to a newer version almost always made NS die horribly, usually in Java... Sometimes you had to go back to the previous library version on one or two of them. After some more experimentation, I found very similar results under both AIX and Digital UNIX. Something tells me that they're doing something funny with memory pointers..... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message