Closed GoogleCodeExporter closed 9 years ago
Not so mysterious; if you have a debug build of tracemonkey, it lets you enable
zealous garbage collection.
Looks like I missed one spot in the usage() for release builds, though -- good
eye!
Original comment by wes%page...@gtempaccount.com
on 15 Mar 2010 at 4:50
We should check for -z whether or not gc zeal is available and print a less
mysterious error message if it's not available.
Original comment by donny.vi...@gmail.com
on 16 Mar 2010 at 1:35
Maybe a -z found in a shebang line should be ignored with a warning. Maybe -z
should
in general just be a warning condition if gczeal isn't available.
Original comment by donny.vi...@gmail.com
on 22 Mar 2010 at 10:01
Agreed. Let's allow -z in option flags all the time, and JS_ReportWarning() or
similar when gcZeal != 0 and #ifndef JS_GC_ZEAL, instead of calling
JS_SetGCZeal().
Checking gcZeal level instead of looking at individual options reduces the
number of
code paths, keeps program behaviour [close to] the same when RELEASE | DEBUG
build
and reduces the number of special cases: overall, a good improvement I think.
Original comment by wes%page...@gtempaccount.com
on 23 Mar 2010 at 2:26
Fixed. Excellent support will have to wait for a JSFEATURE_* API from Mozilla,
but -z
is now exposed all the time, and we complain at compile time if JSAPI was build
without it.
Original comment by wes%page...@gtempaccount.com
on 2 Apr 2010 at 6:21
Original issue reported on code.google.com by
nickgsup...@gmail.com
on 14 Mar 2010 at 5:31