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

Issue 645439 link

Starred by 2 users
Status: WontFix
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Closed: Oct 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

When changing source and saving workspace linked file, devtools disconnects

Reported by remysh...@gmail.com, Sep 9 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2855.0 Safari/537.36

Steps to reproduce the problem:
1. Create a workspace linked project
2. Make a change to a JavaScript asset
3. Save
4. Crashes

What is the expected behavior?

What went wrong?
Crashed/devtools disconnects.

Did this work before? Yes Previous build of canary.

Chrome version: 55.0.2855.0  Channel: canary
OS Version: OS X 10.10.3
Flash Version: Shockwave Flash 23.0 r0

Comment 1 by paulir...@chromium.org, Sep 12 2016

Components: Platform>DevTools>Editing
Labels: -Pri-2 Pri-1
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Thx for reporting, remy.

Last week we pushed a CL that touched workspaces, so I suspect it's that.

Remy, can you open devtools on devtools and check out the console for any logs/exceptions when reproducing this? Also a screenshot of your mapping config in DevTools settings / Workspaces would be great.

lushnikov, anything other info we want?

Comment 2 by paulir...@chromium.org, Sep 29 2016

Components: Platform>DevTools>Authoring

Comment 3 by lushnikov@chromium.org, Oct 4 2016 

Hi Remy,

Does the inspected page crash or devtools? Can you send a crashId?

Comment 4 by remysh...@gmail.com, Oct 4 2016 

I need to get back into the same configuration. I'll give this a go
tomorrow (I switched back to chrome main channel for a while for client
work).

Comment 5 by lushnikov@chromium.org, Oct 24 2016

Labels: -Pri-1 Needs-Feedback Pri-2
Any updates on this? Could you please send a crash report through chrome://crashes if this happens?

Comment 6 by lushnikov@chromium.org, Oct 28 2016

Status: WontFix (was: Assigned)
Won't fix for now - this is not actionable without crash report
►

Sign in to add a comment