Chrome help thread: https://productforums.google.com/forum/#!msg/chrome/W81vPKZXtkg/IO8WYCiuBgAJ

I am experiencing this bug as well. 

Desktop Chrome: 50.0.2661.75 m (64-bit), running on Windows 10 (version 1511, OS Build: 10586.164)

Android Chrome: 49.0.2623.105, running on Galaxy S5 (AT&T), Android version 5.0.1 (Kernel version: 3.4.0-6185444, Build number: LRX22C.I337UCUGOK2)

The same set of steps reproduces the problem for me. I see exactly the same behavior (inspector screen opens, and then closes a split second later).

Same problem here

Thank you, this issue has been confirmed and working to fix it.

The bug we were able to find does not line up with what is reported here. To diagnose this further we need more info. Can we get someone who can recreate this bug to give us a some logs?

see: https://www.chromium.org/for-testers/enable-logging

Thanks!

Sure, I can do this for you -- I'll do this tonight, when I get home and
have access to my dev machine.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/6aa3211e5f2b8a4bbe400e24d448d2ceb4c60115

commit 6aa3211e5f2b8a4bbe400e24d448d2ceb4c60115
Author: reillyg <reillyg@chromium.org>
Date: Wed Apr 27 23:10:31 2016

Support USB transfers from arbitrary threads in the new Linux backend.

DevTools relies on being able to issue USB transfers from an arbitrary
thread and have the callback run back on that thread. This is possible
in the libusb version but not the new native Linux version. This patch
adds the necessary thread hopping logic for that but only for bulk and
interrupt transfers as DevTools only uses those.

BUG= 603434 

Review-Url: https://codereview.chromium.org/1916053006
Cr-Commit-Position: refs/heads/master@{#390227}

[modify] https://crrev.com/6aa3211e5f2b8a4bbe400e24d448d2ceb4c60115/device/usb/usb_device_handle_usbfs.cc
[modify] https://crrev.com/6aa3211e5f2b8a4bbe400e24d448d2ceb4c60115/device/usb/usb_device_handle_usbfs.h

I just tried to replicate this bug with logging enabled, and failed to replicate it. Specifically, it is now working for me to perform remote debugging.

I notice that my desktop Chrome changed versions very slightly:

Now: Version 50.0.2661.87 m (64-bit) (April 27, 2016)
Was: Version 50.0.2661.75 m (64-bit) (April 18, 2016)

My Android Chrome version also changed versions:

Now: Version 50.0.2661.89 (April 27, 2016)
Was: Version 49.0.2623.105 (April 18, 2016)

I also changed USB ports on my development machine between April 18 and April 27, for the USB connection between the desktop and my Galaxy S4 phone. However, I tried several different USB ports, and all were able to support remote debugging today.

FWIW, my adb version is 1.0.32 (Revision 09a0d98bebce-android), and my Android version is still the same.

Sorry I wasn't able to replicate this, though I'm glad to have the feature working again. 

At some point it started working again for me as well. Happy to see it work, sorry I'm not able to help pinpoint what the problem actually was.

Thank you for providing more feedback. Adding requester "allada@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I am going to flag this as fixed. I spoke to reillyg@ and he identified a bug specific to linux and pushed a fix out yesterday. If this regresses again please open a new bug. Thank you!

Issue 607747 has been merged into this issue.

Issue 608093 has been merged into this issue.