[ARGUS] Running out of memory when doing a rasort

[eric]

Ah yes, more fun problems.

During a large spike in traffic, we noticed that rasort dies off
around 500MB being loaded into memory.

$ ls -l argus.2004.04.30.01.10.00.tmp
-rw-r-----  1 me flows  329519468 Apr 30 01:10 argus.2004.04.30.01.10.00.tmp

Turns up with...

rasort[99756]: RaCopyArgusRecord(0xbfbfe990) ArgusCalloc(1, 148) error Cannot
allocate memory

Watching top(1) shows this happens around 500MB being loaded into
memory. 

Some things about the host: it's a FreeBSD 4.9-RELEASE with the
following specs...

CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2399.34-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
real memory  = 1341980672 (1310528K bytes)
avail memory = 1300062208 (1269592K bytes)

Also, swap has about 512MB, but the host doesn't swap out.

Some limits set in /etc/login.conf are....

root:\
        :cputime=unlimited:\
        :datasize=unlimited:\
        :stacksize=unlimited:\
        :memorylocked=unlimited:\
        :memoryuse=unlimited:\
        :filesize=unlimited:\
        :coredumpsize=unlimited:\
        :openfiles=unlimited:\
        :maxproc=unlimited:\
        :sbsize=unlimited:\
        :vmemoryuse=unlimited:\
        :priority=0:\

...though apparently some hard limits are set (including stack size at 
65536 bytes and segment size at 524288 kbytes).

Just curious if folks have seen anything such as this; now, I return
to trying to figure out whats causing a 314MB file to be written :)

- Eric