New issue
Advanced search Search tips

Issue 627550 link

Starred by 2 users
Status: WontFix
Owner:
dominickn@chromium.org
Closed: Jul 2016
Cc:
calamity@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Check failed: score.last_engagement_time() <= rebase_time

Project Member Reported by w...@chromium.org, Jul 12 2016 
I hit this DCHECK consistently on a TOT chrome public Android build. JB Galaxy Nexus. I just loaded storage.googleapis.com/watk/v and it triggers.
 
[FATAL:site_engagement_service.cc(306)] Check failed: score.last_engagement_time() <= rebase_time (2016-07-11 23:04:22.407 UTC vs. 2016-07-05 18:24:04.060 UTC)

dominickn@ could you take a look/reassign?

Comment 1 by dominickn@chromium.org, Jul 13 2016

Cc: calamity@chromium.org
Components: Security>UX
Does this happen when you try a fresh profile? Or only with an existing profile?

If it's an existing profile, how old is it (rough Chrome version when it was created?)

And did you change the clock setting on your phone recently?

It's very odd that you hit this DCHECK, because the branch that it's in should only be triggered if the overall last_engagement_time is more than a week in the fast, but the score.last_engagement_time in your crash is only a couple of days ago (each time the score.last_engagement_time is updated, the global one should be too).

Comment 2 by w...@chromium.org, Jul 13 2016 

Just tried again and it didn't happen.. Not sure what's changed. I guess this is a wontfix then.

Comment 3 by dominickn@chromium.org, Jul 13 2016

Status: WontFix (was: Available)
Reopen if you see this again. :)

Comment 4 by lafo...@chromium.org, Dec 9 2016

Components: -Security>UX
Labels: Team-Security-UX
Security>UX component is deprecated in favor of the Team-Security-UX label
►

Sign in to add a comment