[developers] Memory problems in LOGON batch mode but not interactive mode?

Eric Nichols ericnichols79 at gmail.com
Fri Jul 31 03:42:09 CEST 2009


Sorry to reply to my own mail, but I think I have found the source of  
my problem. After replacing all values of :wait in the LOGON branch to  
3000, my files successfully loaded. I am not sure exactly which  
setting was causing my system to time out, but could I request that we  
consider a higher value for loading large transfer grammars?

Eric Nichols

On Jul 29, 2009, at 10:46 PM, Eric Nichols wrote:

> Greetings,
> I am trying to load a large number  (~100,000) of mtrs in LOGON's  
> batch mode and the lisp process consistently dies about halfway  
> through after it has consumed around 1.3 gigs of memory according to  
> the gc messages. However, the exact same setup works fine in  
> interactive mode, and the lisp process uses over 3 gigs of memory.  
> Does anyone know if there are any drastic differences in memory  
> usage/limitations in batch mode and interactive mode? I am calling  
> batch as follows:
> $ unset DISPLAY && unset LUI && $LOGONROOT/batch --binary --jaen -- 
> ascii tanaka-000.jaen.aa
> I do not have a lisp license, so I cannot try this without --binary.  
> I have attached the log for your reference.
> Thanks,
> Eric Nichols
> <tanaka-000.jaen.aa.fan.log>

More information about the developers mailing list