runtime: negative duration panic in timeHistogram.record #43328
It's possible sometimes for
Notably, this could happen when running under gVisor, where, for efficiency, gVisor provides its own VDSO for acquiring the current monotonic time, but falls back on a different clock if the system clock is wildly in error (https://github.com/google/gvisor/blob/master/vdso/vdso_time.cc#L149).
The result is a panic that can't be worked around. For resiliency's sake,
The text was updated successfully, but these errors were encountered: