Quantcast
Channel: ClearScript
Viewing all articles
Browse latest Browse all 2297

New Post: MemoryLeak despite disposing of V8 Script Engines

0
0
I'm very interested in those fixes! I appreciate how active you guys are on this project still. We're using it for some compelling things :)

It may be that my next move is to wait for your fixes and see where I go from there. If it helps though, I do see some threads that look like this:
OS Thread Id: 0xf260 (17)
Current frame: ntdll!NtWaitForSingleObject+0xa
Child-SP         RetAddr          Caller, Callee
000000002c1bfd10 000007fefd2410dc KERNELBASE!WaitForSingleObjectEx+0x9c, calling ntdll!NtWaitForSingleObject
000000002c1bfd90 000000007712413d ntdll!RtlAllocateHeap+0xd9d, calling ntdll!RtlAllocateHeap+0xdb0
000000002c1bfdb0 000007fee3b46319 *** WARNING: Unable to verify checksum for v8-x64.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for v8-x64.dll - 
v8_x64!v8::ResourceConstraints::code_range_size+0xeb9, calling v8_x64!v8::ArrayBuffer::Contents::Contents+0x26a0
000000002c1bfe40 000007fee3d5f970 v8_x64!v8::ArrayBuffer::Contents::Contents+0x1550
000000002c1bfe70 000007fee8164f7f *** ERROR: Symbol file could not be found.  Defaulted to export symbols for msvcr120.dll - 
msvcr120!beginthreadex+0x107
000000002c1bfea0 000007fee8165126 msvcr120!endthreadex+0x192, calling msvcr120!beginthreadex+0xf0
000000002c1bfed0 0000000076fc652d kernel32!BaseThreadInitThunk+0xd
000000002c1bff00 00000000770fc521 ntdll!RtlUserThreadStart+0x21
So some thread sitting on a Wait within v8-x64.dll. There are a bunch that look like this.

I will continue to play around see if I can come up with a simple reproduction of the run away threads, but not too hopeful I can do it at the moment.

Viewing all articles
Browse latest Browse all 2297

Latest Images

Trending Articles





Latest Images