Subject: Netscape Communicator 4.0beta3: The Borg that ate my computer.
To: None <port-sparc@netbsd.org>
From: Greg Earle <earle@isolar.Tujunga.CA.US>
List: port-sparc
Date: 04/10/1997 18:54:27
netbsd4me:1:51 % netscape-4.0beta3
/usr/local/bin/netscape-4.0beta3: Cannot allocate memory.

ENOMEM?  OK, color me dense.  What's the deal here?

Yes, the Netscape executable is ridiculously huge:

netbsd4me:1:47 % ls -l /usr/local/bin/netscape-4.0beta3
-r-xr-xr-t  1 bin  bin  11714560 Apr  4 13:45 /usr/local/bin/netscape-4.0beta3*

But I've got a 64 Mb machine with 128 Mb of swap space and a 28 Mb MFS /tmp:

netbsd4me:1:56 % pstat -s ; pstat -T ; df /tmp
Device      1K-blocks     Used    Avail Capacity  Type
/dev/sd0b      131480    20388   111092    16%    Interleaved
240/956 files
    485 vnodes
19M/128M swap space
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
mfs:26          29575       84    28012     0%    /tmp

I've tried "unlimit" on everything:

netbsd4me:1:71 % unlimit
netbsd4me:1:72 % limit
cputime         unlimited
filesize        unlimited
datasize        65536 kbytes
stacksize       65536 kbytes
coredumpsize    unlimited
memoryuse       58544 kbytes
descriptors     956 
memorylocked    58544 kbytes
maxproc         276 

But it still doesn't run:

netbsd4me:1:73 % netscape-4.0beta3
/usr/local/bin/netscape-4.0beta3: Cannot allocate memory.

I don't get it.  A sum of all the VSZ fields from "ps -aux" yields 80 Mb.
A sum of the RSS values yields only just over 7 Mb!

Something's wrong here.  What am I missing?  I suppose I could make the MFS
/tmp smaller and reboot, but "pstat" and "df /tmp" certainly aren't telling
me that I'm anywhere near being out of swap.  So why am I getting ENOMEM?

	- Greg