New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 778578 link

Starred by 3 users
Status: Duplicate
Merged: issue 729826
Owner:
kozy@chromium.org
Closed: Dec 2017
Cc:
█ sc00335...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Debugging connection closed when editing Javascript

Reported by helmut.w...@gmail.com, Oct 26 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce the problem:
1. chromium-browser --remote-debugging-port=9222 --user-data-dir=`mktemp -d` http://google.de &
2. chromium-browser --user-data-dir=`mktemp -d` http://localhost:9222
3. select Google -> Sources -> apis.google.com -> cb=gapi.loaded_0
4. In the first line, delete "g" from gapi.
5. wait ~3 sec

What is the expected behavior?
DevTools do not disconnect

What went wrong?
Popup:
   Debugging connection was closed. Reason: WebSocket disconnected
   Reconnect when ready by reopening DevTools.

Did this work before? N/A 

Chrome version: 62.0.3202.62 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)  Channel: n/a
OS Version: Ubuntu 16.04.3 LTS
Flash Version: (Disabled)

It happens on many sites when edititing Javascript, but not all. Also seen on Windows

Comment 1 by manoranj...@chromium.org, Oct 26 2017

Labels: Needs-Triage-M62

Comment 2 by sc00335...@techmahindra.com, Oct 30 2017

Cc: sc00335...@techmahindra.com
Labels: Triaged-ET Needs-Feedback
Unable to reproduce this issue on reprorted chromium 62.0.3202.62 using Ubuntu 14.04 with steps mentioned below.

1.Launched chromium using chromium-browser --remote-debugging-port=9222 --user-data-dir=`mktemp -d` http://google.de
2.Opened devtools and navigated to sources section.
3.Selected cb=gapi.loaded_0 file and deleted "g" from first line. Attaching screenshot for reference.
4.Devtools remain same without disconnecting.

@Reporter: Could you please check the screencast and let us know if we miss anything. This would help in further triaging of the issue. 

Thanks!
Issue 778578.ogv
3.6 MB View Download

Comment 3 by helmut.w...@gmail.com, Oct 30 2017 

You missed step 2 in op: open a second chromium instance to connect to the first one
then edit source in second chromium instance
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 30 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

Comment 5 by eostroukhov@chromium.org, Oct 30 2017

Owner: kozy@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 6 by kozy@chromium.org, Dec 12 2017

Mergedinto: 729826
Status: Duplicate (was: Assigned)
It is live edit issue, we are going to improve it.
►

Sign in to add a comment