Subj : Re: GC-related bug in SpiderMonkey
To   : pavel.cenek
From : Brendan Eich
Date : Fri May 13 2005 02:51 pm

pavel.cenek@gmail.com wrote:
> 
> One more thing that we found - the reportp->filename points to the same
> string as cx->fp->script->filename. It is set in the
> js_ReportErrorNumberVA() function (jscntxt.c) on line 619:
> 
> 617    for (fp = cx->fp; fp; fp = fp->down) {
> 618        if (fp->script && fp->pc) {
> 619            report.filename = fp->script->filename;
> 
> 
> I would be grateful for any comments.


This was bug 291312 -- 
https://bugzilla.mozilla.org/show_bug.cgi?id=291312 in 
bugzilla.mozilla.org.  It has been fixed on the cvs.mozilla.org trunk. 
You can apply the patch in that bug to recent SpiderMonkey releases.

Sorry for the bug, it should have been found by code review.


> We would be also interested in an answer to the following question:
> What is
> the size limit of the pool for GC-things. Is it not limited only by
> available physical memory (apparently not).

The number of GC-thing bytes (including flag bytes) is limited by the 
parameter you pass to JS_NewRuntime.

/be

.