Investigate flaky test-inspector-stop-profile-after-done on Windows

[Trott]

• Version: v11.0.0-pre (master)
• Platform: win2016, vs2017
• Subsystem: inspector

https://ci.nodejs.org/job/node-test-binary-windows/17913/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=2/console

not ok 565 sequential/test-inspector-stop-profile-after-done
 ---
 duration_ms: 0.643
 severity: fail
 exitcode: 1
 stack: |-
 [test] Connecting to a child Node process
 [test] Testing /json/list
 [err] Debugger listening on ws://127.0.0.1:61687/d9182774-879a-41b1-aaff-0365ee4e4d80
 [err] For help, see: https://nodejs.org/en/docs/inspector
 [err] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [out] {}
 [out] 
 [err] Debugger attached.
 [err] Waiting for the debugger to disconnect...
 [err] 
 { AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
 + expected - actual
 
 - 3221225477
 + 0
 at runTests (c:\workspace\node-test-binary-windows\test\sequential\test-inspector-stop-profile-after-done.js:28:10)
 at process._tickCallback (internal/process/next_tick.js:68:7)
 generatedMessage: true,
 name: 'AssertionError [ERR_ASSERTION]',
 code: 'ERR_ASSERTION',
 actual: 3221225477,
 expected: 0,
 operator: 'strictEqual' }
 1
 ...

@nodejs/v8-inspector @nodejs/platform-windows @nodejs/testing

[apapirovski]

The vast majority of our failures are currently from the inspector, I would really like if we could avoid landing more changes to it until we get this situation under control.

[richardlau]

 actual: 3221225477,

This is an access violation, e.g. the test crashed.

[bzoz]

Is this the same as #19263?