Don't use SystemTimeNanos() for current wallclock time on WINUWP
SystemTimeNanos() will soon be replaced with another implementation
when built with Chromium. This will break the assumption of
SystemTimeNanos() being relative to the NTP epoch. To avoid breaking
any UWP apps, call the TimeHelper::Ticks() function directly, which
is synchronized with the NTP epoch during initialization.
Bug: chromium:516700
Change-Id: I4e50cb3f88d06e1385e73b1a9ded52956501dc1f
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/208520
Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org>
Reviewed-by: Niels Moller <nisse@webrtc.org>
Commit-Queue: Johannes Kron <kron@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#33324}
diff --git a/system_wrappers/source/clock.cc b/system_wrappers/source/clock.cc
index 0ae624d..8edffa6 100644
--- a/system_wrappers/source/clock.cc
+++ b/system_wrappers/source/clock.cc
@@ -90,10 +90,10 @@
protected:
timeval CurrentTimeVal() override {
- // The rtc::SystemTimeNanos() method is already time offset from a base
- // epoch value and might as be synchronized against an NTP time server as
- // an added bonus.
- auto nanos = rtc::SystemTimeNanos();
+ // The rtc::WinUwpSystemTimeNanos() method is already time offset from a
+ // base epoch value and might as be synchronized against an NTP time server
+ // as an added bonus.
+ auto nanos = rtc::WinUwpSystemTimeNanos();
struct timeval tv;