Memory management about mini_racer HOT 3 CLOSED

Yes mini_racer is designed to hold almost no refs between VMs. The only refs allowed are an array of procs it is allowed to call.

By avoiding transparently holding references and weak refs to objects between VMS (everything is moved by copy) risk of memory issues goes way down.

from mini_racer.

Thanks, that's good news. One other, related thing: do you plan on supposing dispose on a context?

from mini_racer.

Yes going to add a mechanism to run a context in a block and dispose of all
v8 resources once block is over "burning" the context,

Also maybe simply add a reset method to clear

On Friday, 20 May 2016, koops [email protected] wrote:

Thanks, that's good news. One other, related thing: do you plan on
supposing dispose on a context?

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#5 (comment)

from mini_racer.