If I set up several breakpoints, sometimes when looking for the next continue targets, the ExecutionPoints are not always monotonically increasing (w.r.t. time). here's a small trace from a session against https://replay.io/view?id=6dabd641-7891-470e-b2aa-e6c52e06a7f9 obtained by adding a few breakpoints and then calling Debugger.findResumeTarget on each ExecutionPoint:
INFO:root:Moving forward from 0 to {'point': '3458764449396031495', 'time': 0.005393452348848498, 'frame': [{'sourceId': '95', 'line': 2, 'column': 2}], 'reason': 'breakpoint'}
INFO:root:Moving forward from 3458764449396031495 to {'point': '4611685954002878504', 'time': 0.008090178523272746, 'frame': [{'sourceId': '95', 'line': 4, 'column': 18}], 'reason': 'breakpoint'}
INFO:root:Moving backwards from 4611685954002878504 to {'point': '31224573109202812141809', 'time': 73.03273825575751, 'frame': [{'sourceId': '95', 'line': 17, 'column': 15}], 'reason': 'breakpoint'}
INFO:root:Moving forward from 31224573109202812141809 to {'point': '42752635233766675054906', 'time': 99.99730327382558, 'frame': [{'sourceId': '95', 'line': 22, 'column': 2}], 'reason': 'breakpoint'}
What steps will reproduce the bug?
If I set up several breakpoints, sometimes when looking for the next continue targets, the ExecutionPoints are not always monotonically increasing (w.r.t. time). here's a small trace from a session against https://replay.io/view?id=6dabd641-7891-470e-b2aa-e6c52e06a7f9 obtained by adding a few breakpoints and then calling
Debugger.findResumeTargeton each ExecutionPoint:What do you see instead?
Even though the
times are increasing, the ExecutionPoints are not.Additional information
Fiddling with the protocol directly, I cannot reproduce this from replay.io