New issue
Advanced search Search tips

Issue 821758 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

All tabs but Elements are empty in Remote Debugging / Chrome Dev Tools

Reported by gabriel....@gmail.com, Mar 14 2018

Issue description

OS : MacOS High Sierra 10.13.3 (17D102)
Android : 7.1.2
Brand : Crosscall Action-X3 and Oneplus 5T confirmed

Desktop chrome version : 65.0.3325.146 (official) (64 bits) — Latest at today's date
Android chrome version : 65.0.3325.109 — Latest at today's date

I activated Android USB Debugging

If I browse using Google Chrome on Android, and I open Remote Debugger in my desktop Google Chrome, only the « Elements » tab is working.
I can see the render on the left, html code on Elements tab, but no other tab work.

If I inspect the inspecter, I have issues when loading modules

inspector.js:22 Empty response arrived for script 'chrome-devtools://devtools/remote/serve_rev/@f412f53af6f3abcd6165b6cf0859dad2e88ff87d/console/console_module.js'
evaluateScript @ inspector.js:22
inspector.js:105 Uncaught (in promise) Error: Could not instantiate: Console.ConsolePanel
    at Runtime.Extension._createInstance (inspector.js:105)

And so goes on for data_grid_module.js, formatter_module.js, cm_module.js, har_importer_module.js, network_priorities_module.js, text_editor_module.js, etc.

Note: everything works with my own One Plus One.

I've looked a bit on google and nothing looks to match this issue
 
remote.device.tab.working.jpg
93.0 KB View Download
network.tab.empty.jpg
185 KB View Download
inspecter.inspecter.jpg
925 KB View Download
elements.tab.working.jpg
435 KB View Download
console.tab.empty.jpg
179 KB View Download
As I've seen that on some other bugs, reloading the tab directly from the remote debugging somehow fix the problem, this does not work on this issue.
This bugs is fixed in latest mac version-65.0.3325.162. Please upgrade and let us know the behavior.
Cc: pnangunoori@chromium.org
It is indeed fixed :)
You may close the issue

Comment 5 by mmenke@chromium.org, Mar 15 2018

Status: Fixed (was: Unconfirmed)
May we reopen this issue ? It has indeed been fixed on Chrom* for Linux, but I still have the bug on Chrom* on Mac having updated to 65.0.3325.162 

Sign in to add a comment