Hi Jakob,
I meant it is NOT something is caught by valgrind.
I cannot get valgrind to work on my mac running sierra. But on linux
valgrind finds no concrete leak with the program. By changing the loop
iteration count, valgrind always gives the same results.
On Tuesday, May 15, 2018 at 2:20:20
Yes.
On Fri, May 11, 2018 at 8:47 PM madana gopal
wrote:
> Thanks, ok. let me go through and update. We have both Script.Run() calls
> and vm.runScript() calls in our project.
>
> So, we have to make sure, we are not making any JS calls, when either
> Run() or vm.runScript() going on (as they w
Never mind; that shouldn't be needed, as isolate->Dispose() contains delete
this. Funky!
You said "it can be caught by valgrind". What does Valgrind report?
On Mon, May 14, 2018 at 11:16 AM Jakob Kummerow
wrote:
> One obvious observation is that you don't have a delete isolate; statement
> in t
One obvious observation is that you don't have a delete isolate; statement
in the loop ;-)
On Sat, May 12, 2018 at 8:42 AM YJ wrote:
> Kinda related to this old thread
> https://groups.google.com/forum/#!searchin/v8-users/isolate$20memory|sort:date/v8-users/C_CzX8nSbDU/c4FR8-j6BQAJ
>
> Basically
