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

Issue 839903 link

Starred by 1 user
Status: Duplicate
Merged: issue 838503
Owner: ----
Closed: May 2018
Cc:
█ sindhu.chelamcherla@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Stepping through code after breakpoint

Reported by lvinaja@gmail.com, May 4 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
1. Put a break point in JS
2. Trigger breakpoint
3. Debugger allows 1-2 steps forward and then debugger crashes
4. page dies

What is the expected behavior?
Should be able to continuously debug until I play through.

What went wrong?
Seems any boolean analysis or var assignment causes the debugger to break ...

Did this work before? Yes last

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 10.0
Flash Version:
Trigger breakpoint.png
18.5 KB View Download
Allowed 2 step forwards.png
46.3 KB View Download
Get error.png
4.6 KB View Download
pages dies.png
4.7 KB View Download

Comment 1 by susan.boorgula@chromium.org, May 6 2018

Labels: Needs-Bisect Needs-Triage-M66

Comment 2 by sindhu.chelamcherla@chromium.org, May 7 2018

Cc: sindhu.chelamcherla@chromium.org
Labels: -Needs-Bisect Triaged-ET
Mergedinto: 838503
Status: Duplicate (was: Unconfirmed)
Thanks for filing the issue. As per steps mentioned in C#0, seems this issue is similar to #838503 hence merging into it.

Feel free to undupe if it is not similar.

Thanks!
►

Sign in to add a comment