Consistent DCHECK failure |
|||
Issue description
The following DCHECK keeps failing on Chrome OS 71.0.3571.0.
Not sure when this regressed.
static unsigned long long ToIntegerMilliseconds(TimeDelta duration) {
DCHECK_GE(duration, TimeDelta());
double clamped_seconds =
Performance::ClampTimeResolution(duration.InSecondsF());
return static_cast<unsigned long long>(clamped_seconds * 1000.0);
}
[https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/timing/performance_timing.cc?l=51]
,
Oct 5
I think its been failing for a while. I only reported it now since the webcontent is unusable and my current work needed webcontent for testing.
,
Oct 5
If this is OS-specific problem then it sounds to me like ChromeOS is somehow providing broken timestamps in some cases, which causes the DCHECK to be hit. I can remove it but might need to investigate more on why it's getting hit.
,
Oct 6
Setting component based on OWNERS for performance_timing.cc
,
Oct 9
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/01e413f07ef7d5ba3d66b2dd85c31ebffc038ea8 commit 01e413f07ef7d5ba3d66b2dd85c31ebffc038ea8 Author: Nicolas Pena <npm@chromium.org> Date: Tue Oct 09 19:21:40 2018 Remove DCHECK from ToIntegerMilliseconds() The DCHECK was reported to be hit in Chrome OS. This may be related to new use cases of the method or broken timestamps. Bug: 892751 Change-Id: I4b9ace1aeeefa8467f42e78539b0fa286ee7c4e5 Reviewed-on: https://chromium-review.googlesource.com/c/1265905 Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#598033} [modify] https://crrev.com/01e413f07ef7d5ba3d66b2dd85c31ebffc038ea8/third_party/blink/renderer/core/timing/performance_timing.cc
,
Oct 9
Work is left to dig into why some of these timestamps are negative, but I'll consider that out of the scope of this bug. |
|||
►
Sign in to add a comment |
|||
Comment 1 by npm@chromium.org
, Oct 5