While working on the DevTools profiler, I've noticed that durations are sometimes incorrect. This seems to be vaguely related to high/low priority state updates. Need to track this down more so I'm filing an issue for myself.
return currentSchedulerTime;
  }
   Check if there's pending work.
  findHighestPriorityRoot();
  if (
    nextFlushedExpirationTime === NoWork ||
    nextFlushedExpirationTime === Never
  ) {
    
    
    recomputeCurrentRendererTime();
    currentSchedulerTime = currentRendererTime;
    return currentSchedulerTime;
  }
   There's already pending work. We might be in the middle of a browser
   event. If we were to read the current time, it could cause multiple updates
   within the same event to receive different expiration times, leading to
   tearing. Return the last read time. During the next idle callback, the
   time will be updated.
  return currentSchedulerTime;
}
function requestWork(root: FiberRoot, expirationTime: ExpirationTime) {
  addRootToSchedule(root, expirationTime);
  if (isRendering) {
    
    
    return;
  }
  if (isBatchingUpdates) {