New issue
Advanced search Search tips

Issue 717475 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

"lastrun" erroneously reported for silent browser launches

Project Member Reported by grt@chromium.org, May 2 2017

Issue description

Chrome writes a "lastrun" value to the registry to serve as a means for other components to know when the last time Chrome was run (e.g., gcapi). This value is written during browser process startup, even for silent background launches. Since these launches don't represent the user interacting with Chrome, they should be excluded.

It's also worth considering if "last browser startup" is even the right thing to measure. Perhaps "last user interaction" makes more sense. Does interacting with an app or extension (e.g., Hangouts) count as running Chrome? If not, is there anything other than interacting with a browser window that should count?

It feels like "lastrun" and "dr" (issue 489821) be driven by the same policy, and therefore be in sync.
 
Project Member

Comment 1 by sheriffbot@chromium.org, May 2 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)
Triage: WontFixing for now. If we should fix it, feel free to reopen.

Sign in to add a comment