Assets Component: Only measure duration until component ready when component gets registered |
||||||
Issue descriptionCurrently, we log the duration from when Chrome starts until the assets component is ready to use. This could be misleading in certain edge cases where the users pairs a DD headset after starting Chrome. The duration from starting Chrome until registering the DD headset will be part of the duration. This may give the impression that it takes a long time until the component is ready. Fix this by only starting the timer on Chrome start when a DD headset is paired.
,
Jan 4 2018
,
Jan 4 2018
,
Jan 6 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9cd3f8d42b04aee700e755bce691347dd3b23656 commit 9cd3f8d42b04aee700e755bce691347dd3b23656 Author: Tibor Goldschwendt <tiborg@chromium.org> Date: Sat Jan 06 00:46:46 2018 [vr] Log time from registering assets component until component is ready to use Bug: 792218 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I2d7f8f418d2391623043f71befb1e91d93f51996 Reviewed-on: https://chromium-review.googlesource.com/809232 Reviewed-by: Ilya Sherman <isherman@chromium.org> Reviewed-by: David Dorwin <ddorwin@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#527461} [modify] https://crrev.com/9cd3f8d42b04aee700e755bce691347dd3b23656/chrome/browser/vr/metrics_helper.cc [modify] https://crrev.com/9cd3f8d42b04aee700e755bce691347dd3b23656/chrome/browser/vr/metrics_helper.h [modify] https://crrev.com/9cd3f8d42b04aee700e755bce691347dd3b23656/tools/metrics/histograms/histograms.xml
,
Jan 8 2018
,
Feb 7 2018
,
Jul 4
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tiborg@chromium.org
, Dec 15 2017