On Fri, May 25, 2018 at 11:36 AM, Ryan Bamford <[email protected]> wrote:
> Im probably missing something obvious but im getting a memory leak running a
> very simple test app
>
> #include <iostream>
> #include <v8.h>
>
> using namespace v8;
> using namespace std;
>
> int main(int argc, char* argv[]) {
>
>   V8::Initialize();
>   {
>     HandleScope handle_scope;
>     Persistent<Context> context = Context::New();
>     context->Enter();
>     context->Exit();
>     context.Dispose();
>   }
>   V8::Dispose();
>   return 0;
> }
>
> Have added the valgrind results as image and below is the lsan
>
> Direct leak of 32 byte(s) in 1 object(s) allocated from:
>     #0 0x7fd80976d158 in operator new(unsigned long)
> (/lib64/libasan.so.4+0xe0158)
>     #1 0x7fd8042c0934 in v8::internal::Isolate::Enter()
> (/lib64/libv8.so.3+0x2d1934)
>
> Any help would be appreciated
>
> NOTE: I have to use the version as am deploying to centos 6

You're unlikely to get an answer, 3.14.5 is almost six years old.

You can build newer versions of V8 on centos 6 but you'll need devtoolset.

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to