search

microsoft / deoptexplorer-vscode

A VS Code extension to visualize deoptimizations in your JavaScript and TypeScript code running in V8 (i.e., NodeJS, Edge, Chrome, etc.).
MIT License
747 stars 8 forks source link

Poor performance when handling huge `isolate-v8.log` file #50

Open SukkaW opened 1 month ago

SukkaW commented 1 month ago

For some reason, with the dexnode I end up with an isolate-v8.log file at the size of 232 MiB. 

$ ls -lah isolate-0x150008000-91458-v8.log
-rw-r--r--@ 1 sukka  staff   232M Jul 23 18:24 isolate-0x150008000-91458-v8.log

And I am stuck at this for 8 minutes, yet it is still loading:

image image
SukkaW commented 2 days ago

@rbuckton Hello?

rbuckton commented 2 days ago

NodeJS/v8 will continue writing to the isolate log until the process exits, which can result in very large files and can take a long time to process. Unfortunately, I do not have a solution for this at the moment, so your best option is to try to isolate the scenario you are investigating as much as possible so as to reduce the size of the log file.

SukkaW commented 2 days ago

to reduce the size of the log file

I am profiling my script, the process only runs for 10 seconds, yet it produces 200 MiB of v8 log.

Does it have something to do with the Node.js module register? I am using dexnode -r @swc-node/register to profile my script.