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

Issue 683851 link

Starred by 1 user
Status: Duplicate
Merged: issue 729826
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Jun 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: LiveEdit of devtools-on-devtools hangs and crashes devtools

Project Member Reported by lushnikov@chromium.org, Jan 23 2017 
Chrome Version       : 58.0.2989.0
OS Version: OS X 10.11.6

This are the repro steps on Chrome Canary, Mac OS X:

1. Open https://refinedtheme.atlassian.net/wiki/discover/all-updates
2. Open DevTools
3. Open DevTools-on-DevTools
4. Open "search across all files", search for "CSSRule=class" string
5. There will be a single entry in the inspector.js file. Try to edit the constructor of the CSSRule, e.g. insert 'console.log(1)' in the very first line
6. Hit Ctrl-S to save changes and kick off LiveEdit
7. Observe the first devtools stuck

After a few minutes, the devtools become responsive again. However, they crash momentarily for me. (Crash ID 92f0bded-3f03-40c8-a617-0dae587293ea (Server ID: bbaac9e580000000))

Comment 1 by l...@chromium.org, Jan 26 2017 

I'm able to reproduce with a "debug_devtools = false" build.

For reference, this does NOT seem to be a duplicate of  crbug.com/683335 .  I'm still able to repro the bug even with a patch for the latter applied.

Comment 2 by lushnikov@chromium.org, Jan 26 2017 

Thank you Eric! Indeed, I experience this on Chrome Canary, so "debug_devtools = false".

Comment 3 by kozyatinskiy@chromium.org, Jun 16 2017

Mergedinto: 729826
Status: Duplicate (was: Assigned)
Looks like something wrong with adding console.log.
►

Sign in to add a comment