Subj : JS_ARENAMETER To : netscape.public.mozilla.jseng From : "Stephen Jones" Date : Fri Aug 15 2003 06:22 pm Our application that uses SpiderMonkey has been using copious amounts of memory and in investigating where that memory was going, I ran across JS_ARENAMETER. It appears that the "arenas" are where all the memory is going, but I don't neccesarily understand what an "arena" is and why it's taking so much memory. I tried to dump out the arenas in a method similar to JS_DumpArenaStats, but there were hundreds of arenas, all with similar names, so I ended up concatenating the statistic values for each similarly named arena. Someone please tell me if this is not a valid approach. The concatenated "temp" arena seems to hang around 9MB and the "properties", "note", and "code" arenas seem to be inconsequential, but the "gc-arena" is out of control . . . after about 5 minutes it hits 21 MB and keeps climbing and the "stack" arena hits 5MB and keeps climbing. Looking at the GC Stats, the "currently allocated bytes" climbs to 8MB, then drops to about 100k after a GC and the hash meter stats seem reasonable. What are these different arenas? Why would they continually grow, even after a GC? How can I keep the size of these items to a minimum? What am I doing wrong? Thanks, - Stephen Jones .