Repository navigation
--inspect connection dies before profiler captures trace #7088
Description
- Version: v7.0.0-pre
- Platform:
- Subsystem:
Its a common scenario to profile the execution of a node script. e.g the tsc compiler. The use case is to get a flamechart of the execution of a script. When the script finishes the debugging connection is closed so the flamechart cannot be analyzed.
Expected:
when capturing cpu profiles in inspect mode, the debugging connection should remain open until the profile is fully captured and ready for post analysis. Alternatively there should be a way to tell inspect not to kill the connection once the script finishes.
Activity
ofrobots commentedon Jun 1, 2016
/cc @eugeneo
eugeneo commentedon Jun 8, 2016
I am unable to reproduce the issue. I get a prompt "Waiting for the debugger to disconnect..." whenever I run script to a completion with an inspector connected.
Note that you may be hitting a different issue that we will upload a fix shortly - sometimes V8 inspector does not attach to V8 running long JS script. Have you tried running your application with "--debug-brk" command line switch? It enables inspector connection before running the script.
pavelfeldman commentedon Jun 8, 2016
@eugeneo i can easily repro it. I start with --debug-brk and start profiling while on a breakpoint. App finishes, connections terminates. This is a regression.
nojvek commentedon Jun 13, 2016
I'll try it out to confirm its fixed.
On Monday, June 13, 2016, Ali Ijaz Sheikh notifications@github.com wrote:
inspector: process.exit should wait for inspector