Issue metadata
Sign in to add a comment
|
Disabling Hardware Acceleration causes SSL padlock and extension popups to flicker over a mouse hover
Reported by
sscar...@gmail.com,
May 27 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3096.0 Safari/537.36 Steps to reproduce the problem: 1.Install Chromium v60.0.3110.0 64-Bit 2.Browse to Settings and Disable Hardware Acceleration and restart the browser 3. Browse to google.com and click on SSL padlock and move your mouse over up and down What is the expected behavior? Disabling Hardware Acc. shouldn't cause any such flickering in any UI components and should be rendered normally as expected What went wrong? UI components such as SSL padlock and extensions with popup menus flicker tremendously when hover your mouse over. Did this work before? Yes 60.0.3096.0 (Official Build) (64-bit) Chrome version: 60.0.3096.0 Channel: canary OS Version: 10.0 Flash Version: This is a regression bug and still present in newer builds, so please patch it ASAP!
,
May 27 2017
o/ i have the same problem Google Chrome 60.0.3112.4 (Offizieller Build) canary (64-Bit) (Kohorte: 64-Bit) Überarbeitung 29fc4fec15c718ea79fd656db6bd26f23fc25494-refs/branch-heads/3112@{#8} Betriebssystem Windows JavaScript V8 6.0.286.4 Flash 26.0.0.119 C:\Users\xxx\AppData\Local\Google\Chrome SxS\User Data\PepperFlash\26.0.0.119\pepflashplayer.dll User-Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.4 Safari/537.36 Befehlszeile "C:\Users\xxx\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --flag-switches-begin --enable-gpu-rasterization --enable-zero-copy --ignore-gpu-blacklist --flag-switches-end
,
May 27 2017
it has been like this for around 6 versions now
,
May 27 2017
Which six versions ? This just started recently a week back.
,
May 29 2017
,
May 29 2017
Able to reproduce the issue on Windows-10 using chrome canary 61.0.3114.0 and reported version 60.0.3110.0.This is regression issue, broken in M60. Below is the manual bisect info: Good build:60.0.3096.0 -(Revision:470759). Bad build: 60.0.3097.0 -(Revision:471158). As per revision bisect is not invoked the chrome builds, hence provided chromium bisect CHANGE-LOG URL: https://chromium.googlesource.com/chromium/src/+log/1852efa6e4d9c3353cd43d1815929d46e0f19a70..67fdcd138ad6a6a8c27848b668355f8c571a89a1 Possible suspect: https://chromium.googlesource.com/chromium/src/+/ad1eaa6c4fd1c53f6e4be4da087a8c13a1e84058 Review-Url: https://codereview.chromium.org/2873313002 csharrison@ Could you please look into this issue and please help us to assign this issue to the right owner if not respect to your change. Note:Issue is specific to Windows-10. Thanks.
,
May 29 2017
I'm the person who made that WebM in Comment 1 originally on the uMatrix extension repo on GitHub https://github.com/gorhill/uMatrix/issues/788 Can confirm that it happens on the Windows 10 in both v60 dev and v61 canary with Hardware Acceleration off (and can't enable it as it horribly lags and causes other issues on my Acer Aspire Z PC with Intel Celeron integrated Graphics). OS: Windows 10 Fall Creators Update (Redstone 3) Insider Preview Build 16199.1000
,
May 29 2017
My change should not have altered rendering like this, I think https://codereview.chromium.org/2867913002 is more suspicious. ericrk would you take a look?
,
Jun 3 2017
So have you found the cause ?
,
Jun 6 2017
Please try a per revision bisect.
,
Jun 6 2017
This is due to my change, already tracked in bug 720105 . A fix is in progress.
,
Jun 7 2017
Thanks, let me know when it's fixed.
,
Jun 8 2017
The fix has landed, this should now be fixed in Chrome 61 (Canary). I'll try to merge to M60 (Beta) today.
,
Jun 9 2017
Thanks. Can you post the revision of the fix, so I would know which to download.
,
Jun 9 2017
comment #12 linked the incorrect bug, this should have been duplicated to bug 729363
,
Jun 9 2017
Re #15 - This fix is currently in: Chrome canary 61.0.3124.10 It has been merged to beta, and will be in the next beta: Chrome Beta > 60.0.3112.24 But you may have to wait until next week for an updated beta.
,
Jun 9 2017
I'm on Canary branch, so will I still have to wait a week ?
,
Jun 9 2017
If you update to the latest Canary, I expect this to be fixed (check your about:version to ensure you are on a version >= 61.0.3124.10). Can you confirm? Otherwise this might be a different issue and we'll have to investigate further. Thanks for the help!
,
Jun 10 2017
I'm on 61.0.3126.0 (Official Build) (64-bit) Yes, it's fixed and I can no longer reproduce it. Thanks. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sscar...@gmail.com
, May 27 2017337 KB
337 KB View Download