I've noticed the GC problem that you mention as well. To me it seems very much that when objects travel between V8 and Python is when problems begin to crop up

I've noticed the GC problem that you mention as well. To me it seems very much that when objects travel between V8 and Python is when problems begin to crop up. Sadly, I have yet to be able to fix this. I believe this issue captures it most concisely: https://code.google.com/p/pyv8/issues/detail?id=193 https://code.google.com/p/pyv8/issues/detail?id=193 I'll have to see about publishing my work publicly, as I don't explicitly own it. My biggest piece of advice is to always build from the latest branched version of v8, rather than the trunk. Right now, that would be 3.23. The branched version tends to be a bit more stable than the trunk. Sadly, since the PyV8 maintainer works from the trunk, I've often had to build a few revs back to get things to compile if there was a major structural v8 change. If you'd be willing to share the details of your build environment, I can see if my work is even applicable and go about getting the permission to publish what I've done. BTW, I want to be clear that in no way am I disparaging the PyV8 maintainer. He's been very responsive and helped fix some problems that would have taken me weeks to fix on my own. The project simply isn't focused on stability at the moment.