New issue
Advanced search Search tips

Issue 878624 link

Starred by 1 user
Status: Fixed
Owner:
chengx@chromium.org
Closed: Aug 31
Cc:
grt@chromium.org
finnur@chromium.org
peter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Toast activator CLSID in shortcut suddenly became incorrect in Canary

Project Member Reported by chengx@chromium.org, Aug 29 
OS: Win10

According to UMA, the toast activator CLSID suddenly became incorrect for increasing number of Canary users starting from August 13. This issue doesn't exist in Beta/Dev/Stable. This would force the notification to go back to the non-native way for those Canary users.

The metric is Notifications.Windows.StartMenuShortcutStatus, and the enum is StartMenuShortcutStatus::kToastActivatorClsidIncorrect as in chrome/installer/util/install_util.cc
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 30 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7255318a9a96170a9c800d4edf3bc1aef7b6f189

commit 7255318a9a96170a9c800d4edf3bc1aef7b6f189
Author: Xi Cheng <chengx@chromium.org>
Date: Thu Aug 30 02:23:22 2018

Record Notifications.Windows.ToastActivatorCLSIDMismatchReason

This metric gives more details about case kToastActivatorClsidIncorrect
of Notifications.Windows.StartMenuShortcutStatus.

Bug:  878624 
Change-Id: I3f1c68df4cae33b5b2de8d8d75581e5ab758a8b9
Reviewed-on: https://chromium-review.googlesource.com/1195680
Commit-Queue: Xi Cheng <chengx@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#587421}
[modify] https://crrev.com/7255318a9a96170a9c800d4edf3bc1aef7b6f189/chrome/installer/util/install_util.cc
[modify] https://crrev.com/7255318a9a96170a9c800d4edf3bc1aef7b6f189/tools/metrics/histograms/enums.xml
[modify] https://crrev.com/7255318a9a96170a9c800d4edf3bc1aef7b6f189/tools/metrics/histograms/histograms.xml

Comment 2 by chengx@chromium.org, Aug 31

Status: Fixed (was: Assigned)
It looks like this strange issue is gone now.
►

Sign in to add a comment