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
fix(browser): Use drift-corrected time origin for INP, replay and profiling
`timestampInSeconds` re-derives its time origin when it detects clock drift,
but `browserPerformanceTimeOrigin` caches the origin resolved at SDK init and
never revisits it. Consumers that convert a `PerformanceEntry`'s monotonic
`startTime` to wall clock time therefore end up on a different timeline than
span and event timestamps once a correction has happened.
Exposes the corrected origin as `correctedPerformanceTimeOrigin` and uses it
for the consumers that outlive a span timeout: INP (reports on pagehide) and
replay (sessions run up to an hour). Profiling already compensated for the SDK
changing its time origin, but computed the adjustment against the stale cached
value.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments