|
Re: [Sbcl-help] Possible SAP memory leak
From: Nikodemus Siivola <nikodemus@ra...> - 2009-01-11 14:51
|
On Wed, Dec 31, 2008 at 10:22 PM, Simon Handley <shandley_42@...> wrote: > I'm trying to track down a possible memory leak associated with SAPs, and > I'm hoping that someone else has already seen this and I've just stupidly > missed an obvious solution in the list archives. I'm 90% sure that (most of?) the leak your test exhibits is actually caused by test itself: without your code you can see that the test conses quite a bit itself. I'm thinking that when your code is loaded it simply conses even more, and some things end up inopportunely tenured -- and finally you run out of space. Looking at the generation breakdown I'm thinking that (GC :GEN 2) after MAP-ALLOCATED-OBJECTS should be sufficient to unkink this. (What you are seeing is the result of an unfortunate combination of issues in MAP-ALLOCATED-OBJECTS and the generational GC.) Additionally, I would strongly suggest passing T as the third argument to MAP-ALLOCATED-OBJECTS. Cheers, -- Nikodemus |
| Thread | Author | Date | |
|---|---|---|---|
| [Sbcl-help] Possible SAP memory leak | Simon Handley <shandley_42@ya...> |
|
|