Greetings,
I think there is a memory leak. I constructed the enclosed lisp files and compiled memtest2.lisp. On a clean abcl evocation I load "try.lisp" and run the various tryN functions. I've mainly been using N=10. You can see that there is a leak when running memtest2. This leak would kill my app after ongoing usage.
On another note, memtest2.lisp creates 1000 functions. If you change the number to 10,000 it can't be compiled. This speaks to the error that was reported recently.
Thanks.
Blake McBride
Greetings,
I think there is a memory leak. I constructed the enclosed lisp files and compiled memtest2.lisp. On a clean abcl evocation I load "try.lisp" and run the various tryN functions. I've mainly been using N=10. You can see that there is a leak when running memtest2. This leak would kill my app after ongoing usage.
On another note, memtest2.lisp creates 1000 functions. If you change the number to 10,000 it can't be compiled. This speaks to the error that was reported recently.
Thanks.
Blake McBride
Hi Blake,
I think there is a memory leak. I constructed the enclosed lisp files and compiled memtest2.lisp. On a clean abcl evocation I load "try.lisp" and run the various tryN functions. I've mainly been using N=10. You can see that there is a leak when running memtest2. This leak would kill my app after ongoing usage.
Since your tests were rather minimal in the code they actually trigger, I was intrigued. And even though I had other actions planned for tonight, I looked into the issue: Well, I found it and fixed it in r13132. The fix is on trunk now and (try3 10) returns a nearly constant "Used bytes" output upon successive invocations!
Hope this gets you back on track with your app!
On another note, memtest2.lisp creates 1000 functions. If you change the number to 10,000 it can't be compiled. This speaks to the error that was reported recently.
Bye,
Erik.
armedbear-devel@common-lisp.net
-
Blake McBride -
Blake McBride -
Erik Huelsmann