[armedbear-devel] changes to autoloading affecting PermGen space?

Erik Huelsmann ehuels at gmail.com
Tue Sep 4 17:59:57 UTC 2012

Hi Alan, Alessio,

On Tue, Sep 4, 2012 at 9:22 AM, Alessio Stalla <alessiostalla at gmail.com>wrote:

> On Tue, Sep 4, 2012 at 6:45 AM, Alan Ruttenberg
> <alanruttenberg at gmail.com> wrote:
> > I've recently been getting
> >
> > ; Evaluation aborted on #<JAVA-EXCEPTION java.lang.OutOfMemoryError:
> > PermGen space {2D9FD5EA}>.
> >
> > I'm wondering whether it is possible that the recent changes to
> > autoloading are filling more of this space, leading to my (and
> > presumably others at some point) errors.
> Well, unless you're using tons of Java libraries, PermGen exhaustion
> in ABCL pretty much implies a memory leak (such as many functions
> never getting garbage collected). I don't know if that can be caused
> by autoloads or not, though.

The autoloads change simply means that several thousand instances of the
Java class org.armedbear.lisp.Autoload are being instantiated instead of
several hundred. I don't see how that would affect PermGen space.

Could it be that your own project has surpassed some critical size?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/armedbear-devel/attachments/20120904/bf0e08b8/attachment.html>

More information about the armedbear-devel mailing list