Blank profiles panel when debugging node
Reported by
raina...@gmail.com,
May 4 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3080.5 Safari/537.36 Steps to reproduce the problem: 1. `node --inspect --debug-brk` then browse to the provided debugger URL in chrome (same happens if NiM launches the debugger) 2. Switch to the Profiles tab 3. Observe blank panel and lots of errors in the console (see attached .log) What is the expected behavior? I expect to see the Profiles tab populated so I can start a JS profile that will resume the break setup with --debug-brk (so I can profile my app startup). What went wrong? I've tested heavily with Version 60.0.3080.5 (Official Build) dev (64-bit) and Version 60.0.3089.0 (Official Build) canary (64-bit) and the behavior can be seen in both. If I switch to the Profiles tab and then reload the page, it populates. If I then close the tab with Ctrl-W and reopen, it continues to work because the Profiles tab is loaded first (I see it flash up THEN I'm taken to the Sources tab. I've found that when I use nodemon with NiM (which causes a hosted devtools session to be opened any time a node debugger is available and nodemon causes my app and the debugger to restart when code changes), I can often restart the app and when the devtools is reconnected, that will also get the Profiles panel to load up, but the errors look to occur (most of them anyway) in the console regardless. Did this work before? N/A Chrome version: 60.0.3080.5 Channel: dev OS Version: 10.0 Flash Version: Shockwave Flash 26.0 r0 I've included 2 console .log files. One is a fresh launch where Profiles doesn't load and the other is a reload where Profiles does load, but there is still a lot of errors in the console.
,
May 5 2017
,
May 10 2017
What version of the Node.js are you using? This used to be an issue with older versions and had been gone since.
,
May 10 2017
When this was reported, I was on 6.10.2. I just updated to 6.10.3 (current release) to see if it remains and it does for both the following clients: Version 60.0.3088.3 (Official Build) dev (64-bit) Version 60.0.3095.0 (Official Build) canary (64-bit)
,
May 10 2017
All 6.10 versions seem to have this issue... There is no way to fix it as the 6.10 require an old version of the Chrome DevTools.
,
May 11 2017
"6.10 require an old version of the Chrome DevTools" there's no fixing this issue in that older version? To be clear, this "WontFix" status is coming from the only team who has the ability to address this right? It's important to be clear I think because 6.10.x is the LTS branch so if the only people who CAN address the issue "Wont", then I take that as a declaration that the LTS Branch of node.js won't get the same developer/debugging support (bug-fixes, not features) that newer node branches can. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, May 5 2017