Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 8ab89c5b authored by Steve Fung's avatar Steve Fung Committed by ChromeOS Commit Bot
Browse files

metrics: Fix metrics_daemon Meminfo callback interval

With the switch from the glib run loop to base::MessageLoop, the
interval for scheduling Meminfo callbacks was incorrectly set to
milliseconds.  Fix it back to seconds.

BUG=chromium:445573
TEST=strace shows metrics_daemon sleep for 30 seconds between
     collecting statistics

Change-Id: I4b4b597273d3cf04b9972011dd0a7386ea14233d
Reviewed-on: https://chromium-review.googlesource.com/238466


Reviewed-by: default avatarChih-Chung Chang <chihchung@chromium.org>
Reviewed-by: default avatarAlex Vakulenko <avakulenko@chromium.org>
Commit-Queue: Steve Fung <stevefung@chromium.org>
Tested-by: default avatarSteve Fung <stevefung@chromium.org>
parent e86591e5
Loading
Loading
Loading
Loading
+2 −2
Original line number Diff line number Diff line
@@ -776,7 +776,7 @@ void MetricsDaemon::ScheduleMeminfoCallback(int wait) {
  base::TimeDelta waitDelta = base::TimeDelta::FromSeconds(wait);
  base::MessageLoop::current()->PostDelayedTask(FROM_HERE,
      base::Bind(&MetricsDaemon::MeminfoCallback, base::Unretained(this),
                 base::TimeDelta::FromMilliseconds(kMetricMeminfoInterval)),
                 waitDelta),
      waitDelta);
}

@@ -795,7 +795,7 @@ void MetricsDaemon::MeminfoCallback(base::TimeDelta wait) {
  if (reschedule) {
    base::MessageLoop::current()->PostDelayedTask(FROM_HERE,
        base::Bind(&MetricsDaemon::MeminfoCallback, base::Unretained(this),
                   base::TimeDelta::FromMilliseconds(kMetricMeminfoInterval)),
                   wait),
        wait);
  }
}