New issue
Advanced search Search tips

Issue 884227 link

Starred by 1 user
Status: Fixed
Owner:
chengx@chromium.org
Closed: Nov 8
Cc:
lfg@chromium.org
grt@chromium.org
brucedaw...@chromium.org
finnur@chromium.org
robliao@chromium.org
peter@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug

Blocking:
issue 882622



Sign in to add a comment

Endless loops in Win10 native notification are triggered in certain OS versions

Project Member Reported by chengx@chromium.org, Sep 14 
OS: Win10

According to brucedawson@'s analysis from a ETW heap trace, endless loops in Win10 native notification display/dismiss are triggered in a Windows machine with OS build 16299. This is likely happening on OS build 15063 and 14393 as well, as indicated by some UMA metrics.

We should try to understand what triggers the endless notification loops.

Comment 1 by chengx@chromium.org, Sep 14 

See https://bugs.chromium.org/p/chromium/issues/detail?id=882622#c30 for details of brucedawson@'s analysis. TL;DR sentences copied over as below.

TL;DR
* Lucas' machine leaks about 24 KB of memory at a time
* The *frequency* of these leak events is extremely high at times, sometimes as high as ~17.7 invocations of chrome.dll!NotificationPlatformBridgeWinImpl::Display per second. 17.7 leaks/s * 24 KB/leak = 424.8 KB/s leaked
* It is possible that the leak itself happens on all versions of Windows 10 but that the notification *spinning* is specific to 16299 and before
* It is quite possible that this is related to  crbug.com/878823  which was a separately reported bug where the notification code would spin endlessly on some Citrix machines

Comment 2 by chengx@chromium.org, Sep 14

Cc: robliao@chromium.org

Comment 3 Deleted

Comment 4 by robliao@chromium.org, Sep 26

Labels: Hotlist-DesktopUIConsider

Comment 5 by robliao@chromium.org, Sep 27

Labels: Group-Notifications

Comment 6 by robliao@chromium.org, Sep 28

Labels: M-71 Target-71

Comment 7 by robliao@chromium.org, Sep 28

Labels: -Hotlist-DesktopUIConsider Hotlist-DesktopUITriaged

Comment 8 by chengx@chromium.org, Nov 8

Status: Fixed (was: Assigned)
On 11/05/2018, Microsoft confirmed this was caused by an IXmlDocument interface issue which was resolved in the latest build. It had to do with the pointers the older code was using.
►

Sign in to add a comment