New issue
Advanced search Search tips

Issue 614028 link

Starred by 6 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Aero snap freezes Chrome on Windows 10

Reported by agildeh...@gmail.com, May 23 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
0. Ensure Aero snap is enabled (System > Multitasking control panel).
1. Open content that is continually causing visible draws, like a YouTube video.
2. Resize Chrome window vertically, dragging to the very top of the screen.
3. Aero snap will cause the window to resize to fill the vertical space.  Mp freeze should occur at this point.
4. Release mouse.
5. Grab the top vertical resize handle again, which should be at the very top edge of your screen, and drag upwards (off the screen).

What is the expected behavior?
No freeze.

What went wrong?
All draws to the Chrome window seem to cease.  Input continues to work.

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0

This likely is related to closed  bug 516234 .
 
One other way to trigger this bug:

1. Drag a window to the left or right edge of the display to snap it along that edge.
2. Using the mouse, begin to resize the snapped window from its top edge. Drag down a few hundred pixels, then drag it back up all the way to the very top of the display. Let go of the mouse button.

Comment 2 by threa...@gmail.com, Jul 18 2016

Another simple way to trigger this:

1. Maximize Chrome
2. Snap Chrome to the left by pressing WinKey+LeftArrow
I am seeing this with windows that I snap (i.e. the behavior that comment #2 describes). The way to get it to refresh/unfreeze is to switch active focus to another window, then back to this window - that seems to cause a redraw. 

Comment 4 Deleted

Comment 5 by threa...@gmail.com, Sep 15 2016

This appears to be fixed in 54+

Comment 6 by jayach...@gmail.com, Sep 18 2016

Still have this issue on latest official release 53.0.2785.116 m

Will try a beta 54...
Can someone confirm if beta 54 solves this, just started having this issue on Version 53.0.2785.116 m (64-bit).

Comment 8 by threa...@gmail.com, Sep 24 2016

I think this is the same as  issue 562681 . I've tried the current beta (54) on two different machines and it appears fixed.
Project Member

Comment 9 by sheriffbot@chromium.org, Sep 25 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment