I haven't been paying enough attention to this site as of late, but I have been keeping busy. Recently I have returned to spending time working on my hobby engine "Plaster". I have primarily been working on the interface between C++ and Javascript and writing up some wrapper code for working with V8. I know there are a few libraries out there already that look pretty good for this, but really I wanted the experience of interacting more directly with V8.

This has been going pretty well, and I am more or less happy with the how it is shaping up (there are a few small things I would still like to change). That is it was going pretty well until I turned on leak tracking (using Visual Leak Detector)... and then bam tons of spew about all kinds of memory leaks. Bummer.

Diving in to it further I ended up stripping things down to try and come up with simple test cases that would cause memory leaks and eventually found that simply entering main and making a call to v8::V8::Dispose before returning (i.e. not touching my code at all) was enough to see a memory leak. I did some searching around and found an entry for this on the V8 issue tracker but there hasn't been any movement on it since May 2.

I'll be digging in to it a little further later on, but I wanted to throw this out here in case in the meantime there is anyone reading this with any experience on the subject that could shed some light.