
TimeTicks should only be used to measure local duration (same machine, same process) and not absolute time. TimeTicks may not increment during process suspension (this is platform dependent) and so TimeTicks created at different time do not share a common reference. As a consequence, it is not possible to convert them to absolute times. WebContents::LastActiveTime is intended to represent the date of the last activation time, that will be persisted and sent to sync. Because it uses TimeTicks, this field is incorrectly synced for WebContents created on Mac or ChromeOS machines. Convert the field to a base::Time to fix it. Convert the field to a base::Time to fix it. Bug: 349542284 Change-Id: Iba85b1579f8ee9ec22d60219c8f8f444eef3336d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5735384 Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: Sylvain Defresne <sdefresne@chromium.org> Cr-Commit-Position: refs/heads/main@{#1338463}