validation appears to leak memory about jsv

[garycourt]

Due to the features in JSON Schema, all schemas must be cached after creation. To clean up your memory, destroy (dereference) the environment after you are finished validating.

[davepacheco]

That's a fair point. So I ran a slightly modified test:

var input = {};
var count = 0;

for (;;) {
    env = mod_jsv.JSV.createEnvironment()
    env.validate(input, schema);
    if (++count % 1000 === 0)
            console.log(count);
}

I also ran this for about 18000 iterations, and the ::findjsobjects output now shows:

> ::findjsobjects
OBJECT   #OBJECTS #PROPS CONSTRUCTOR: PROPS
...
fd0d0bf5      240     10 <anonymous> (as Components): errors, scheme, ...
fc0e4171      304      1 Object: type
fd0ce3a5      408      2 ReplaceResultBuilder: special_string, elements
 8044ead      421      1 Object: <unknown>
fc0d7901     1014      0 Object:
fc0bf8b1     1494      7 JSONSchema: _value, _env, _fd, _uri, _refs, ...
fc0c195d     8717      4 JSONInstance: _value, _env, _fd, _uri

This certainly looks a lot better. Since there's less than one object per validation, maybe these objects are actually garbage that hasn't been collected yet.

Additionally, after 3 minutes and 10000+ iterations, the VSZ and RSS haven't really grown much beyond about 30MB. Thanks!