GitLab

This CL attempts to handle the unexpected situation we were CHECKING for.

The windows native window occlusion finch experiment is causing a lot
of check fails with |window_is_moving_| true when we receive a EVENT_SYSTEM_MOVESIZESTART
event. I'm unable to reproduce this, but this CL should prevent us from getting stuck
in the |window_is_moving_| state while still avoiding calculating occlusion during moves.

Also attempt to detect when we've possibly missed an end move event, because we
got an unexpected event while we think we're moving, and set |window_is_moving_| to false.

I've also moved the setting of |window_is_moving_| to false at the start of UnregisterEventHooks
in the unlikely event that UnhookWinEvent is causing the event hook callback to get called
reentrantly. Some crash reports show UnregisterEventHooks on the stack, but looking at the
same crash dump in VS doesn't show UnregisterEventHooks.

Bug: 907365
Change-Id: Iec41dbbe656d0acea0c161b45ec5b7812eb32233
Reviewed-on: https://chromium-review.googlesource.com/c/1348829Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611240}