tab removal, ignore
Unbust MSVC build.
Fix leak of active handlers in continuation.

If a continuation is never resumed but it saved handlers, they would
never become active again and would thus be leaked.
Update probe.pm

Using the newer 'make_path' and 'remove_tree' causes build/configure to bail out on older versions of File::Path (especially those shipped with perl v5.10). Please see [File::Path#APIChanges][1]

[1]: https://metacpan.org/pod/File::Path#API-CHANGES
Clear up gen2 memory at exit.
Don't leak static frame instruction offsets.
Clear up frame pool at exit.
Avoid leaking 72 bytes per MVMHash.

In gc_free for MVMHash, due to HASH_CLEAR clearing the head pointer,
we ended up never freeing the memory for the first node in a hash.
Simplify frame refcount handling in continuations.

Avoid a couple of seemingly unrequired fiddles. Doesn't help with the
frame leak, but simpler/cleaner.
Fix a source of frame leaks in continuations.

When we GC a continuation that sliced off some active handlers, and
those handlers still reference frames, make sure we decrement the
frame reference count. Can happen for a gather/take that does not
ever complete its execution. So, not the big leak affecting all of
the gather/takes, but a needed fix anyway.
Missing frame dec ref on exception resume.

Active handler's frame reference goes away, so decrement.
Fix "on stack" continuation ref-count handling.

When a frame is on the current call stack, it gets its reference count
incremented by 1 to indicate it's active at the very least as a result
of currently being running. When we take a continuation, to make sure
frame lifetimes are handled correctly, we just decrement this count as
we slice frames away. Similarly, continuation invoke should re-instate
the count as we splice the frames back onto the active call stack.
Fixes gather/take memory leak reported by TimToady++.
Some missing cleanup in MAST compiler.
Merge pull request #79 from svatsan/patch-1

Update probe.pm
Don't leak named_used in MVMCallCapture.

This caused over 300,000 1-byte leaks in CORE.setting compilation.
Don't leak C string in library lookup.
Don't leak C string in bytecode loading.
check for invalid code points (jvm port)