Repository navigation
takeHeapSnapshot in node inspect creates corrupted JSON #56
Description
- Version: v8.8.1
- Platform: Darwin 17.3.0 Darwin Kernel Version 17.3.0: Thu Nov 9 18:09:22 PST 2017; root:xnu-4570.31.3~1/RELEASE_X86_64 x86_64
- Subsystem: node inspect
I am trying to use "node inspect" to attach to the already running node process to collect the heap dump. Using the command:
takeHeapSnapshot(filepath = 'node.heapsnapshot') Take a heap snapshot and save to disk as JSON.
The command seems to be completed successfully.
debug> takeHeapSnapshot(filepath = 'node.heapsnapshot')
Heap snaphost prepared.
Wrote snapshot: /Users/aleksander/node.heapsnapshot
But afterwards I am trying to open it in "Node.js V8 --inspector Manager (NiM) 0.14.5" it throws the following error:
An error occurred when a call to method 'buildSnapshot' was requested
TypeError: Cannot read property 'length' of undefined
at HeapSnapshotWorker.JSHeapSnapshot.initialize (chrome-devtools://devtools/bundled/heap_snapshot_worker.js?experiments=true&v8only=true&ws=localhost:9229/803f37dc-c1b9-409f-8705-530077f269f7:897:1641)
at new HeapSnapshotWorker.JSHeapSnapshot (chrome-devtools://devtools/bundled/heap_snapshot_worker.js?experiments=true&v8only=true&ws=localhost:9229/803f37dc-c1b9-409f-8705-530077f269f7:1090:412)
at HeapSnapshotWorker.HeapSnapshotLoader.buildSnapshot (chrome-devtools://devtools/bundled/heap_snapshot_worker.js?experiments=true&v8only=true&ws=localhost:9229/803f37dc-c1b9-409f-8705-530077f269f7:1197:85)
at HeapSnapshotWorker.HeapSnapshotWorkerDispatcher.dispatchMessage (chrome-devtools://devtools/bundled/heap_snapshot_worker.js?experiments=true&v8only=true&ws=localhost:9229/803f37dc-c1b9-409f-8705-530077f269f7:1247:509)
When I open the generated dump it seems to be a corrupted JSON ending prematurely with:
",2,8443,81187,32,1,0
,1,46,81189,32,"
Is this a node inspect bug? I am able to succesfully connect to the same instance of node by the browser and use the "Take heap snapshot" function where the generated dump opens without any problems. Also noticed that the properly generated dump has about 80MB where the corrupted one only 800K.
I thought that maybe I am doing something wrong but since no error is reported and we end up with the corrupted JSON this seems to be an issue...
Activity
addaleax commentedon Jan 17, 2018
Yeah, I think so. The issue is that
node-inspectthink the expected output size is given by thetotalfield of the heap snapshot stats, but in reality it’s the item count, not the data length.I think the only way to reliably tell whether the
addHeapSnapshotChunkdata stream has ended is actually inspecting the JSON data itself and looking for the closing}. :/aleksanderlech commentedon Jan 18, 2018
I did that and it this is the way file ends:
",2,8443,81187,32,1,0 ,1,46,81189,32,"which makes it invalid JSON for sure :)
fix: Make `takeHeapSnapshot()` work
fix: Fix `takeHeapSnapshot()` truncation bug