Garbage Collector not working about pyv8 HOT 8 OPEN

Update: I remember seeing warnings about dtrace missing when I was building v8. 
Could this make the difference? I've found this pyv8 binary maintainer's commit 
that seems to link the two issues together: 
https://github.com/taguchimail/pyv8-linux-x64/commit/aaae4b4c2cac88bc78a87e711c8
18bed7a6bccd6. 

I've tested it with this binary distribution now - same effect. My solution for 
now will be to monitor the PyV8 process and restart it on OS level when the 
memory consumption has become too high.

Since taguchimail's binary repo comes with a 'stable' branch (PyV8 429 / V8 
r10452), I had to try this out as well. This has been an improvement as in the 
empty evals at least didn't show a leak anymore - the whole application still 
leaks however, so I'm trying to isolate new test cases now. In other words, the 
reported behavior above must have come in somewhere between 429 and 557. 

[deleted comment]

[deleted comment]

[deleted comment]

[deleted comment]

Update: Wrapping the JSContext inside the wrapper as posted below and using 
PyV8 r428 / V8 r10452 solves the memory leak issues for me. I have to say 
though that the garbage collection is relatively slow this way, so I have to do 
it in a background process.