Subj : Re: GC-related bug in SpiderMonkey
To   : netscape.public.mozilla.jseng
From : pavel.cenek
Date : Sat May 14 2005 02:09 am

Brendan,

thank you for the lightning-fast answer!

Regarding the JS_NewRuntime's maxbytes parameter - it makes sense to me
now, however, I find the documentation a little bit unclear in this
matter. It says: "maxbytes specifies the number of allocated bytes
after which garbage collection is run".

We interpreted it as that it is a threshold after which GC is run
(which implied questions like how much memory is allocated for the GC
things, when GC will be called again if GC does not free enough memory
to get under the threshold, etc.)

It would be helpful to mention in the JS_NewRuntime documentation that
this is the upper memory limit and that the GC is launched
automatically only if there is no more memory for GC-thing allocation
and that the application itself should call JS_GC or JS_MaybeGC
regularly.

Is it possible to update the documentation in this way? It would IMO
help SpiderMonkey integrators a lot.

   Pavel

.