Like with discarding/freezing logic, we also want session restore to only track elapsed time while Chrome is in use, rather than absolute time. This allows for session restore logic to make smarter decisions.

It might also make sense to only advance time on a per-profile basis, so that a profile that sits in the background rarely used doesn't advance time at the same right as another profile that is actively used.

If a profile has an opened window, I think it makes sense to advance time in it while any chrome window is in-use (other profile or not). Otherwise we'll reclaim tabs from the active profile before the inactive one...

What I was saying offline is that if a profile is not loaded (or has zero windows I guess because Chrome never unloads profiles during a session). Then when it's opened weeks later, it shouldn't forgo loading its tabs solely because the rest of chrome has been in-use.