doug@clarity.Princeton.EDU (Douglas Merrill) (06/21/91)
We just started running Lucid Common Lisp 4.0 under SunOS 4.1.1, and have been having problems with running out of memory, garbage collection failures, and bus errors. Our network includes a Sun 4/280 fileserver and several SparcStation2's -- recently upgraded. Each SparcStation has about 32Mb of swap space. When running lisp code which formerly (under Lucid Lisp 3.0) worked
doug@clarity.Princeton.EDU (Douglas Merrill) (06/21/91)
We just started running Lucid Common Lisp 4.0 under SunOS 4.1.1, and
have been having problems with running out of memory, garbage
collection failures, and bus errors. Our network includes a Sun 4/280
fileserver and several SparcStation2's -- recently upgraded. Each
SparcStation has about 32Mb of swap space.
When running lisp code which formerly (under Lucid CL 3.0) worked for
even very large datasets, we are finding that it now runs out of
memory even with smaller ones. Usually it terminates with a message
like this:
;;; Failed to re-enable EGC after the memory manager disabled it for memory
;;; reorganization:
;;; EGC could not be enabled because the dynamic GC is disabled.
>>Error: GC and EGC disabled: not enough storage after GC. CONSers
are now using the storage normally reserved for copying
currently allocated dynamic storage.
and sometimes even:
;;; Ran out of Memory during GC
Process lisp stopped (signal)
Our best guess is that garbage collection is simply failing to get rid
of things it needs to get rid of, because
1) We've run bigger things on the earlier version
2) It shouldn't break with this kind of fatal error if it is working
correctly.
Has anyone else encountered a similar problem? Has a bug fix been
published to correct this problem?
Please email any suggestions or answers to ghn@clarity.Princeton.EDU
(I'm posting this for him.)
If there's enough interest, I'll post a summary to the net.
Douglas Merrill
doug@clarity.princeton.edu
Princeton Univ.
Cognitive Science Labbarmar@think.com (Barry Margolin) (06/21/91)
In article <DOUG.91Jun20163342@clarity.princeton.edu> doug@clarity.Princeton.EDU (Douglas Merrill) writes: >We just started running Lucid Common Lisp 4.0 under SunOS 4.1.1, and >have been having problems with running out of memory, garbage >collection failures, and bus errors. Get the patch to bug 5648. The description I have of this patch is "code reorganization/bug fixing in egc.lisp". -- Barry Margolin, Thinking Machines Corp. barmar@think.com {uunet,harvard}!think!barmar
lange@lanai.cs.ucla.edu (Trent Lange) (06/21/91)
In article <1991Jun21.055722.22249@Think.COM> barmar@think.com writes: >In article <DOUG.91Jun20163342@clarity.princeton.edu> doug@clarity.Princeton.EDU (Douglas Merrill) writes: >>We just started running Lucid Common Lisp 4.0 under SunOS 4.1.1, and >>have been having problems with running out of memory, garbage >>collection failures, and bus errors. > >Get the patch to bug 5648. The description I have of this patch is "code >reorganization/bug fixing in egc.lisp". >-- >Barry Margolin, Thinking Machines Corp. Is there an ftp site where this and other Lucid Common Lisp 4.0 patches are available (we're having some of the same problems)? - Trent Lange -- ************************************************************************** * UCLA Computer Science: Get a Ph.D. in ten years, or your money back. * **************************************************************************
kriegman@klaupacius.eng.yale.edu (David Kriegman) (06/21/91)
>We just started running Lucid Common Lisp 4.0 under SunOS 4.1.1, and >have been having problems with running out of memory, garbage >collection failures, and bus errors. Our network includes a Sun 4/280 >fileserver and several SparcStation2's -- recently upgraded. Each >SparcStation has about 32Mb of swap space. There is a bug in Sun Common Lisp 4.0 that causes this problem. After wrestling with this problem for nearly 3 months, I finally got a patch from Sun and it cleared up the problem. Give them a call. -Dave
barmar@think.com (Barry Margolin) (06/22/91)
In article <1991Jun21.095713.3895@cs.ucla.edu> lange@lanai.cs.ucla.edu (Trent Lange) writes: >In article <1991Jun21.055722.22249@Think.COM> barmar@think.com writes: >>Get the patch to bug 5648. >Is there an ftp site where this and other Lucid Common Lisp 4.0 patches are >available (we're having some of the same problems)? I know of no FTP site for Lucid patches. Lucid sends them to us in email responses to bug reports. We deal directly with Lucid rather than going through Sun for Lisp S/W support. I'm trying to find out whether we have a special arrangement that allows us to do this (perhaps we're a VAR) or whether any Sun CL customer can; if the latter, I'll post the email address. -- Barry Margolin, Thinking Machines Corp. barmar@think.com {uunet,harvard}!think!barmar