You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b9aa06f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(replay): Drop the buffer at too-long jumps and re-read raced segment requests
Buffer mode now drops what it recorded before a forward wall-clock jump
longer than sessionDuration: the pre-jump frames, touch events and
already buffered segments. It keeps recording on the new timeline, so an
error soon after no longer sends one replay spanning hours or years.
Session mode already stops at the same jump.
Segment requests (pause, flush, stop, configuration change, error flush)
read their times when made, so a busy executor doesn't stretch the
segment. If a frame moved the recording onto a new timeline in between,
those times and the frames the task finds were on different timelines:
a backward jump could produce a frozen segment minutes long, and a
buffer flush right after a forward jump could stretch one frame over the
whole jump. The strategies now track the timeline their queued work is
on, and a request's task reads its times again on that timeline when it
differs from the one the request read. Without a jump nothing is re-read,
so every value stays what it was.
resume() no longer re-anchors the clock. Otherwise every request until
its queued task runs would look like it raced a jump. A jump while
paused is followed by the first frame after resume, like any other.
Refs GH-6522
Refs JAVA-829
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
0 commit comments