Unable to reproduce the issue on MAC 10.11.6 using chrome stable #53.0.2785.116 and latest canary #55.0.2873.0.
Attached a screen cast for your reference.

Following are the steps followed to reproduce the issue.
------------
1. Create account at https://www.icloud.com/
2. Logged into and clicked "Keynote" app
3. Clicked the "+" button and clicked cancel 10 times.
4. Observed that dialog eased in on center of the page as expected.


Reporter@ - Could you please check this issue on chrome stable #53.0.2785.116 and latest canary #55.0.2873.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Deleted: 650484.mp4 8.6 MB

	650484.mp4 8.6 MB View Download

Yes, issue occurs with Chrome stable #53.0.2785.116 and with canary #55.0.2873.4 by creating a new profile without any apps and extensions.

So far we are only seeing it only on some hardware (MacBookAir4,2) but not iMacs or retina MacBook Pro.

Not sure if this is the correct component, please remove/update if incorrect.

Thank you for providing more feedback. Adding requester "krajshree@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

This reminds me of another bug that only manifested on specific MacBook Air machines. https://bugs.chromium.org/p/chromium/issues/detail?id=571256

CCing ccameron@ for insight on what may have changed in Mac rendering M54 to M55.

Could test try to confirm the issue on the specific hardware (Mac Air)?

Can you attach a PDF print-out of about:gpu from the affected machine?

I wonder if this is because this is on a GPU-blacklisted machine.

It looks very similar to issues where we re-use an IOSurface while the WindowServer is still using it. We're still vulnerable to that issue on GL and software renderer, and we did recently move HD3000 GPUs to software renderer.

Unable to reproduce the issue on Mac air 10.116 using chrome latest stable 54.0.2840.71 and canary 56.0.2905.0 with the steps attached in comment #0.
Not observed any flickering while clicking on + button and cancel option.
Please find the attached screen cast for the same.

siulung@Could you please once try the issue on latest stable and update the thread if the issue still persists.

removing Needs-TestConfirmation.please feel free to add if required.

Thanks,

Deleted: 650484.mp4 11.2 MB

	650484.mp4 11.2 MB View Download

I need to increase the swap-chain length in SW mode.

Yes, we are still seeing it with Chrome 54.0.2840.98 running on macOS 10.12.1 on a 2011 13-inch MacBook Air with Intel HD Graphics 3000 384MB with built-in display at 1440x900 HiDPI resolution. It happens around 30% of the time when the "+" button is clicked.

I still need to make the swap chain longer in SW mode.

 Issue 715303  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/469d0548dfb4c3304c03571ba3f0f1a9bc58e2a4

commit 469d0548dfb4c3304c03571ba3f0f1a9bc58e2a4
Author: ccameron <ccameron@chromium.org>
Date: Sat May 06 19:15:44 2017

Use more than double buffering in SoftwareOutputDeviceMac

Previously, this would flip between two buffers, but that had issues
because the IOSurfaces would sometimes still be being read by the
window server while the next frame was writing (leading to flashes).

Change this to a buffer queue very similar to the GPU output surface
BufferQueue. Use the IOSurfaceIsInUse function to ensure that buffers
are not painted to until they are not being read by the window server.

Limit the number of buffers being held in the queue to 4 (determined
empirically). If we need more than 4, then they will thrash (by
frequent allocation and discard). The window server will keep more
than 4 IOSurfaces alive (as many as it needs) regardless of our
purging here.

BUG= 650484 

Review-Url: https://codereview.chromium.org/2866683003
Cr-Commit-Position: refs/heads/master@{#469876}

[modify] https://crrev.com/469d0548dfb4c3304c03571ba3f0f1a9bc58e2a4/content/browser/compositor/software_output_device_mac.h
[modify] https://crrev.com/469d0548dfb4c3304c03571ba3f0f1a9bc58e2a4/content/browser/compositor/software_output_device_mac.mm
[add] https://crrev.com/469d0548dfb4c3304c03571ba3f0f1a9bc58e2a4/content/browser/compositor/software_output_device_mac_unittest.mm
[modify] https://crrev.com/469d0548dfb4c3304c03571ba3f0f1a9bc58e2a4/content/test/BUILD.gn

Great, will try Monday's canary and see if this resolves the issue I am seeing.

 Issue 735185  has been merged into this issue.