New issue
Advanced search Search tips

Issue 787992 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Inspect button in chrome://inspect/#devices is doing nothing

Reported by jase.wil...@gmail.com, Nov 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. Navigate to chrome://inspect/#devices
2. Assuming you have a device set up with Node (8.9.0) running in inspect, click inspect
3. Nothing is happening

What is the expected behavior?
The console should pop up, or at least some error as to why it can't communicate with the device

What went wrong?
Yesterday this was working, but now its failed on both my Mac and my PC, on version 62 and Canary (64).

There's no error, so i have little to work with, there's also no error in the dev tools console.

Did this work before? Yes Yesterday but im not sure what version my Chrome was running then

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 10.0
Flash Version:
inspect.gif
45.9 KB View Download

Comment 1 by jase.wil...@gmail.com, Nov 22 2017 

If it helps I've restarted the Node application (after it running constantly for 2 days) and its working now. So this should rule out any firewall/network issue.

Does inspect stop working once if the application has been running for too long? or if the memory usage goes over a certain point?

Comment 2 by manoranj...@chromium.org, Nov 22 2017

Labels: Needs-Triage-M62

Comment 3 by krajshree@chromium.org, Nov 23 2017

Labels: Needs-Bisect

Comment 4 by sc00335...@techmahindra.com, Nov 27 2017

Labels: -Needs-Bisect Triaged-ET
As per comment#1 issue seems to be fixed after restarting node application. Hence removing Needs-Bisect label.

Requesting someone from Platform>Devtools team take a look into this issue as per C#1.

Thanks!

Comment 5 by pfeldman@chromium.org, Nov 27 2017

Status: WontFix (was: Unconfirmed)
Can't repro - we need a good set of scenarios to address it. I understand that providing reliable repro for something that takes two days is not easy, but we need to start somewhere in order to address it...
►

Sign in to add a comment