The ReplayManager tries to temporarily suppress breakpoints before (re-)starting replay and resumes the debugger in case the debugger is paused. This interacts poorly with time-indexed outputs because starting playback will race with unsuppressing breakpoints, and some breakpoint hits may be missed.
Instead, we should probably just issue Debugger.stepOut commands until nothing is left in the call stack, and then restart replay.
There may be some way to blow over the call stack using exceptions or something, but this could have a lot of unwanted side effects in the UI.
Maybe the best fix on on the backend? ReplayAgent can talk directly to the debugger and only pause when needed.
Closing web replay-related bugs until we resume working on the feature again.