Unable to stop profiler recording in dedicated devtools on chrome://inspect page.
Reported by
yfulgaon...@etouch.net,
Feb 16 2017
|
|||
Issue descriptionChrome Version : 58.0.3013.3 (Official Build) f3229ac11997e2b5fe740be8738c2ac80ab9f4c3-refs/branch-heads/3013@{#6} 32/64 bit OS : Windows (7,8,10), Mac(10.11.6, 10.12.1, 10.12), Linux(14.04 LTS) What steps will reproduce the problem? 1. Launch chrome, navigate to chrome://inspect and click on "Open dedicated DevTools for Node" (Devtools window appears). 2. In devtools window, navigate to 'Profiler' tab and click on 'Start' button. (Recording starts) 3. Now click on 'Stop' button and observe. Actual : Unable to stop recording under 'Profiler' tab. Expected : User should be able to stop the recording. This is a non-regression issue, seen from M-57 series as this is a new feature introduced in build #57.0.2987.0.
,
Feb 17 2017
Seems that we should be able to stop or disable the Profiler when there isn't any node target available. eostroukhov@, could you please take a look?
,
Mar 2 2017
Is your application waiting for IO (e.g. waiting for a socket connection, timer, etc)? In this case it might be this bug: https://github.com/nodejs/node/issues/11589 Can you provide more details? Do you start with "--debug-brk" (or --inspect-brk)? Are you running Node script to completion?
,
Apr 14 2017
Closing as not enough information was provided (see comment #3). Suspected issue on the Node side was fixed. |
|||
►
Sign in to add a comment |
|||
Comment 1 by msrchandra@chromium.org
, Feb 16 2017