Chrome currently binds remote debugging to the "127.0.0.1" address. This fails in the IPv6-only environment.
Issue 597371 has been merged into this issue.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ff8289e0123c7829ae54581e96e70bfdfe9882ab commit ff8289e0123c7829ae54581e96e70bfdfe9882ab Author: pfeldman <pfeldman@chromium.org> Date: Fri Apr 01 21:59:47 2016 DevTools: remote debugging should work in the IPv6-only environment. BUG= 599915 TBR=sky (for trivial browser change) Review URL: https://codereview.chromium.org/1846953007 Cr-Commit-Position: refs/heads/master@{#384702} [modify] https://crrev.com/ff8289e0123c7829ae54581e96e70bfdfe9882ab/chrome/browser/browser_process.h [modify] https://crrev.com/ff8289e0123c7829ae54581e96e70bfdfe9882ab/chrome/browser/chrome_browser_main.cc [modify] https://crrev.com/ff8289e0123c7829ae54581e96e70bfdfe9882ab/chrome/browser/devtools/remote_debugging_server.cc [modify] https://crrev.com/ff8289e0123c7829ae54581e96e70bfdfe9882ab/chrome/browser/devtools/remote_debugging_server.h
Comment 1 by samu...@chromium.org
, Apr 1 2016