Stephen Maher (maher++at++holodeck.gsfc.nasa.gov)
Tue, 9 Feb 1999 12:22:58 -0500 (EST)
Chances are your compilation of convasd is 32 bit, which will konk out
around 1.8GB. Use "file convasd" to check. Try recompiling for 64
bit (-64).
Steve
-- stephen.maher++at++gsfc.nasa.gov (301) 286-3368 fax:(301) 286-1776 http://holodeck.gsfc.nasa.gov/vr/vr.html NASA Goddard Space Flight Center
Kenneth R. Sewell III writes: > > I'm in the final stages of finishing my ASD terrain. The last step is > to run it through convasd. The problem is that convasd requests ~2GB of > memory (as I previously posted). I was able to clear up enough disk > space that I could set up 2 GB of virtual swap (the machine only has 512 > of main memory). When I run swap -s it lists the proper amount > available, however when I run convasd it gives me the same message about > not having enough memory: > > PF Fatal/Resource: pfMemory::new() Unable to allocate > 2627774384 bytes from arena 0x4b4b4000. > Try using pfSharedArenaSize() or env PFSHAREDSIZE > to increase the arena size > (currently 732421.88 KBytes) and check for adequate setrlimit() > values and available space on swap (or pfTmpDir()). > > Swap -s reports: > total: 0.00k allocated + 84.05m add'l reserved = 84.05m bytes used, > 2.41g bytes available > > and my environment has: > PFSHAREDSIZE=3000000000 > > >From what I read in the perfomer manuals, it should work with this > setup. Am I missing something? > > Ken > Sewell++at++siscom.net > > > ======================================================================= > List Archives, FAQ, FTP: http://www.sgi.com/software/performer/ > Submissions: info-performer++at++sgi.com > Admin. requests: info-performer-request++at++sgi.com >
This archive was generated by hypermail 2.0b2 on Tue Feb 09 1999 - 09:24:00 PST