Issue metadata
Sign in to add a comment
|
Native tooltip on transparent Chromium window eating up abnormal GPU usage
Reported by
animethe...@gmail.com,
Jun 13 2016
|
||||||||||||||||||||||
Issue description
Chrome Version : 51.0.2704.84 ("Electron" win32 official prebuilt)
OS : Windows 10 Home x64
What steps will reproduce the problem?
(1) Open Electron with a transparent BrowserWindow.
(2) Move the mouse cursor around those HTML elements with a "title" attribute so that the native tooltip is displayed.
What is the expected result?
Tooltips should display properly with no impact on GPU usage.
What happens instead?
At certain point, the display of tooltip would mess up somehow (incomplete message displayed, tooltip leaving behind without disappearing, etc) and the GPU usage would skyrocket, sometimes even locking up the display of other windows.
The problem is demonstrated in the following video.
https://www.youtube.com/watch?v=nmrKkt8Xefg
The Electron demo appeared to be normal at first with normal GPU usage, but when I started to move around the cursor to toy with the tooltip on the lower left corner (0'52"), the display of tooltip would mess up at certain point, and the GPU load and memory controller load began to skyrocket, which not only slowed its own display but also locked up the display of other windows. The problem persisted until the window was minimized or closed (or when the tooltip window naturally disppeared).
The problem is still there even if I replace it with a much simpler animation. It doesn't seem to have much relationship with the nature of the content. As long as the window is large enough and there are some tooltips to display, the problem will show up sooner or later.
The problem does NOT seem to appear on a NON-transparent window. Also, the problem occurs only on versions of Chromium above 49 (the last I tried was 49.0.2623.75, without any problem).
PS: I filed this bug on Electron's side first, but the admin over there thought this should be a regression bug on Chromium's side, and suggested I file the bug report here instead.
Electron Github:
https://github.com/electron/electron
,
Jun 17 2016
After more tests, I have managed to figure out the simplest steps to reproduce the problem. 1) Open an Electron (Chromium 50+) window in transparent mode. 2) Open a page with some elements that contain the "title" attribute. 3) Resize the window after page load (using something like window.resizeBy(640,480)). 4) Move the cursor around the page so that those tooltips are shown. At certain point, the GPU usage will suddenly rise noticeably. --------------- For your convenience, you can repdroduce the problem with the following steps. 1) Download Electron v1.2.2 win32 ia32 https://github.com/electron/electron/releases/download/v1.2.2/electron-v1.2.2-win32-ia32.zip 2) Download the attached "app.zip" and unzip it to "resources" folder. 3) Run "electron.exe" and it will open a transparent window with the page "_tooltip.html". Move the cursor around those links so that the tooltips are displayed. At certain point, the problem should occur.
,
Jun 18 2016
Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 27 2016
==================================== Good Build: 49.0.2623.0 Base Position: 369907 Bad Build: 50.0.2633.0 Base Position: 371964 ===================================== Able to repro this issue on Windows 10 [Pro] for the Google Chrome Stable Version - 52.0.2743.82 This is a regression issue broken in M50, below mentioned is the bisect info: CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/49.0.2623.0..50.0.2633.0?pretty=fuller&n=10000 Suspecting Commit: fb33c340bd50b0e8a5c874e5d7c10a6361cee126 Review URL: https://codereview.chromium.org/1608733002 @scottmg: Could you please look into the issue, and if it has nothing to do with your changes and if possible please do assign it to the concerned owner. Thank you.
,
Jul 27 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 10 2016
,
Mar 3 2017
The bisect range in #4 is rather large (~2000 revisions), can we get a narrower bisect?
,
Jun 21 2017
Somehow, I am unable to reproduce this issue on Windows-10, latest stable chrome version: 59.0.3071.109. Didn't observed any spike in memory usage when hoving over the link in _tooltip.html page. Attached is the screen-cast of the same. @reporter: Could you please confirm if this issue is still relevant on the latest stable version?
,
Jul 31 2017
Removing from Bisect bucket since TE was not able to repro in latest chrome version.
,
Aug 11 2017
,
Mar 9 2018
No feedback -> closing |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rnimmagadda@chromium.org
, Jun 16 2016Labels: Needs-Feedback