Unable to reproduce the issue on Windows 10 with chrome #61.0.3163.100 as per steps mentioned in the comment #0

Attaching the screen-cast for reference.

luzar.david@ Could you please look into it and let us know any steps i have missed while reproducing the scenario.

Deleted: 768207.mp4 8.0 MB

	768207.mp4 8.0 MB View Download

You've done everything correct.

Maybe your colleagues will help shed some light as they've been able to repro the same issue (?) here:

https://bugs.chromium.org/p/chromium/issues/detail?id=767842 and here:
https://bugs.chromium.org/p/chromium/issues/detail?id=768134

Nevertheless, I've re-recorded the screencast with more info:

Deleted: 44dfab4e-cbb8-4d04-yf3c-3be9183107d2.webm 10.6 MB

	44dfab4e-cbb8-4d04-yf3c-3be9183107d2.webm 10.6 MB View Download

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

As sidenote, happens in devTools, too (which probably makes sense):

Deleted: chrome61_opacity_bug_devTools.gif 340 KB

	chrome61_opacity_bug_devTools.gif 340 KB View Download

Looks like there are a couple of duplicates that bisect to the same patch. So marking this as a duplicate.

luzar.david: Do you have an intel graphics card? Can you attach the content of about:gpu here?

If you do have an intel card, if you disable gpu rasterization in about:flags, does the issue still reproduce?

Unduplicating because this is Windows only, which makes it seem a lot like  issue 755871 .

I don't have Intel card, but disabling GPU rasterization *works*. Solves every rendering regression since v61, including DevTools buttons rendering issue I reported here: https://bugs.chromium.org/p/chromium/issues/detail?id=768209

Attaching about:gpu output

Deleted: gpu.htm 51.9 KB

gpu.htm 51.9 KB View Download

Thanks! about://gpu says ANGLE (NVIDIA GeForce GTX 750 Direct3D11 vs_5_0 ps_5_0), which makes me a little suspicious.

Can you try one other thing? Can you run chrome with gpu rasterization enabled, but passing the command line flag --disable-d3d11 to Chrome?

See https://www.chromium.org/for-testers/command-line-flags for information about adding command line flags if you're not familiar with doing that.


bsalomon: Sorry to keep passing bugs your way, but can you take a look at this? It seems suspiciously like things you've been looking at recently.

Running with flag --disable-d3d11 (and GPU rasterization *enabled*) solves the issue, too.

Unable to reproduce the issue on Windows 10(NVIDIA drivers) with chrome #61.0.3163.100 as per steps mentioned in the comment #0

Attaching the screen-cast & GPU for reference.

Since TE doesn't able to reproduce the scenario, adding TE-NeedsTriageFromMTV for further triage

pbommana@ Could you please look into it.

Deleted: 768207-gpu.html 53.4 KB

768207-gpu.html 53.4 KB View Download

Deleted: 768207.mp4 8.8 MB

	768207.mp4 8.8 MB View Download

Duplicate of 755871?

This doesn't appear to be a duplicate of  crbug.com/755871  since it is reproducible on non-Intel GPUs (according to comment #12).

The d3d11 comment does make this sound like this is potentially an angle / driver issue though, even if it's separate from the previous intel clearing bug.

 Issue 768209  has been merged into this issue.

luzar.david@ could you see if the 63.0.3234.0 canary fixes this problem?

It contains a fix for a seemingly related issue ( crbug.com/768134 ).

confirming 63.0.3234.0 did solve this, and every related bugs I had :)

Re-duplicating this into 768134 since it appears to be just a different manifestation of the ANGLE/D3D11 clipping bug.