Re: Memory leak in vec (and maybe persistent!)?

On Aug 19, 2:38 am, Christophe Grand wrote: > Imagine a persistent data structure S1 with a root node A and two child > nodes B and C. > On this data structure you call transient, make some updates and call > persistent! which yields an updated persistent data structure S2 with the > root node

Re: Memory leak in vec (and maybe persistent!)?

Hi Andy! On Tue, Aug 18, 2009 at 8:43 PM, Andy Fingerhut < andy_finger...@alum.wustl.edu> wrote: > > On Aug 17, 3:51 am, Christophe Grand wrote: > > Why do you focus on these AtomicReferences? If you contrast pre-transient > > vectors and actual vectors you'll see that the overhead due to instan

Re: Memory leak in vec (and maybe persistent!)?

On Aug 17, 3:51 am, Christophe Grand wrote: > On Sat, Aug 15, 2009 at 4:23 PM, Andy Fingerhut < > > andy_finger...@alum.wustl.edu> wrote: > > Not to say this ought to be done, but would it be possible to have no > > 'edit' field *at all* for persistent data structures (not even a null > > referen

Re: Memory leak in vec (and maybe persistent!)?

On Sat, Aug 15, 2009 at 4:23 PM, Andy Fingerhut < andy_finger...@alum.wustl.edu> wrote: > Not to say this ought to be done, but would it be possible to have no > 'edit' field *at all* for persistent data structures (not even a null > reference), and only an edit field at the "root" data structure

Re: Memory leak in vec (and maybe persistent!)?

On Aug 15, 5:44 am, Christophe Grand wrote: > I wouldn't call this a memory leak: vectors have a bigger memory overhead > than before (additional PersistentVector$Node and AtomicReference). > > On Sat, Aug 15, 2009 at 2:13 AM, Andy Fingerhut < > > andy_finger...@alum.wustl.edu> wrote: > > When I

Re: Memory leak in vec (and maybe persistent!)?

I wouldn't call this a memory leak: vectors have a bigger memory overhead than before (additional PersistentVector$Node and AtomicReference). On Sat, Aug 15, 2009 at 2:13 AM, Andy Fingerhut < andy_finger...@alum.wustl.edu> wrote: > When I did this, one of the first several lines of output include

Memory leak in vec (and maybe persistent!)?

If there is a better place to report things like this, let me know. I've done some looking at how much memory various kinds of Clojure data structures use, and come across some behavior that I think might be a memory leak, in the sense that perhaps a reference to a java.util.concurrent.atomic.Ato