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

New Post: MemoryLeak despite disposing of V8 Script Engines

0
0
I don't think it is right, but I'm not sure how to get the correct symbols. Here's the 'noisy' output from windbg. I added a MS and Chrome symbol path:
000007fe`fda210dc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtWaitForSingleObject+0xa
SYMSRV:  d:\symbols\v8-x64.pdb\AEFF2A3642C44ACE9BB070E1CFCFCC8D1\v8-x64.pdb not found
SYMSRV:  https://msdl.microsoft.com/download/symbols/v8-x64.pdb/AEFF2A3642C44ACE9BB070E1CFCFCC8D1/v8-x64.pdb not found
SYMSRV:  d:\symbols\v8-x64.pdb\AEFF2A3642C44ACE9BB070E1CFCFCC8D1\v8-x64.pdb not found
SYMSRV:  https://chromium-browser-symsrv.commondatastorage.googleapis.com/v8-x64.pdb/AEFF2A3642C44ACE9BB070E1CFCFCC8D1/v8-x64.pdb not found
DBGHELP: C:\Projects\!OPEN_SOURCE\clearscript\ClearScript\V8\V8\build\v8-x64\build\Release\v8-x64.pdb - file not found
*** WARNING: Unable to verify checksum for v8-x64.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for v8-x64.dll - 
DBGHELP: v8_x64 - export symbols
Where does v8-x64 come from?

Viewing all articles
Browse latest Browse all 2297