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

Issue 696840 link

Starred by 1 user
Status: WontFix
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Break points not working when debugging

Reported by yurki...@gmail.com, Feb 28 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce the problem:
1. Added breakpoint 
2. Reloaded page
3. File with breakpoint closed

What is the expected behavior?
Shouldn't close the file so it can stop at the breakpoint.

What went wrong?
I can't debug because of this. 

Did this work before? Yes 

Chrome version: 56.0.2924.87  Channel: stable
OS Version: OS X 10.10.5
Flash Version: 

This one is hard to reproduce. It doesn't happen all the time.

Comment 1 by nyerramilli@chromium.org, Feb 28 2017

Labels: Needs-Triage-M56

Comment 2 by pfeldman@chromium.org, Feb 28 2017

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

Comment 3 by kozyatinskiy@chromium.org, May 19 2017

Status: WontFix (was: Assigned)
I think it was related to old workspace implementation and should be fixed for now. Feel free to reopen it or file new issue if it's still a problem.
►

Sign in to add a comment