A handful of my users have been complaining about this on our application, but I hadn't been able to reliably reproduce it until now.

The JSFiddle link in the original post triggers the issue for me on the first click, without having to bring up additional modals (though those do reproduce the issue as well). I'm running Windows 7 with Chrome 61.0.3163.100 (64-bit).

This issue goes away if I disable hardware acceleration in settings > advanced.

I'm unable to reproduce with Chrome 61, with hardware acceleration enabled.

I can't repro on Win10.

Maybe this only presents in certain device. Here is a copy of my chrome://gpu

Deleted: gpu.html 52.0 KB

gpu.html 52.0 KB View Download

Attached is a copy of my chrome://gpu as well.

Deleted: gpu.htm 52.2 KB

gpu.htm 52.2 KB View Download

By now, we use:

.modal-content,.modal-header,.modal-body, .modal-footer{
background-color:white;
}

To avoid render error, until google solve it.

exact the artifacts I`ve mentioned on  issue 770354 

Adding a video of this happening to our application.

So far we've only been able to reproduce this on machines without dedicated GPUs. Furthermore, of the machines it's reproduceable on, it's only been so on the primary monitor (laptops). On these machines we've had success with disabling hardware acceleration.

Deleted: artifacting.mp4 197 KB

	artifacting.mp4 197 KB View Download

>>So far we've only been able to reproduce this on machines without dedicated GPUs [...] On these machines we've had success with disabling hardware acceleration.

I also resolved by disabling hardware acceleration. Even though the first appearance of these artifacts was on my laptop, using the main monitor and NVIDIA GTX 1050 dedicated graphics, other computers with the Intel 4000 Graphics (in which I not certain if its dedicated) also had the same bug.

also, I was able to solve by changing the background from 

background-color: #000

to

background-color: rgba(0,0,0,1)

See also https://github.com/twbs/bootstrap/issues/24233#issuecomment-334471177

Bootstrap (see comment above)'s users have been able to consistently reproduce what we believe is the same issue. The artifacts can be observed in http://jsfiddle.net/1aeur58f/1/ unless hardware acceleration is disabled. The linked to issue includes some addition details.

I am having the same issue https://www.screencast.com/t/bUG01qhiR
url is http://webapplayers.com/inspinia_admin-v2.6/modal_window.html

@vasil, I use the same theme (Inspinia) in one of our applications, and we are also having this issue

So far, this appears to only be occurring on Intel 0x0a16 - HD 4400. If you're experiencing this issue please attach the contents of "about:gpu" (navigate to about:gpu, save as website, complete). This will help us narrow this down.

mummareddy@, can you help with a repro? Do we have any machines with an HD4400 GPU? On the hardware list I see an HD4300 and HD4500, might be worth trying those to see if we get the same issue.

jmadill@, this seems like a hardware-specific Windows issue. Have you seen anything like this before?

I am having the same issue. 
I checked, and my hardware is like you mentioned.
I attach here the GPU file.
Also, I'll note that this does not happen on other browsers like Edge.
Thanks!

Deleted: chrome___gpu.pdf 117 KB

chrome___gpu.pdf 117 KB Download

Experiencing the issue on my HP Elitebook 850 G1 with Intel HD4400 gpu

Deleted: gpu.htm 52.5 KB

gpu.htm 52.5 KB View Download

Same issue, here is my chrome://gpu 
(I have an HD Graphics 4400 too)

Deleted: gpu.htm 55.5 KB

gpu.htm 55.5 KB View Download

I also have this issue, but with Intel HD Graphics 4600.
I can't post the entire chrome://gpu output, but I can provide a few pieces below.

Data exported	10/24/2017, 2:00:43 PM
Chrome version	Chrome/61.0.3163.100
Operating system	Windows NT 6.3.9600
Software rendering list version	13.10
Driver bug list version	10.29
ANGLE commit id	0d2ecb4ea992
2D graphics backend	Skia/61 0eefc0552cfb5ac077560b7c2630c5bd475ea585-
Command Line	"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end

GPU0	VENDOR = 0x8086, DEVICE= 0x0416 *ACTIVE*

GL_VENDOR	Google Inc.
GL_RENDERER	ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0)
GL_VERSION	OpenGL ES 3.0 (ANGLE 2.1.0.0d2ecb4ea992)

manoranjanr@, do you know if the test lab has any HD4400 machines on which we could try to reproduce? On the hardware list I see an HD4300 and HD4500, might be worth trying those to see if we get the same issue.

 Issue 777341  has been merged into this issue.

Duplicate  bug 777341  has some additional test cases.

Seems like i could able to repro this on HD 4600 (Win7) for M63. Fortunately this doesn't exists on Latest Canary#64.0.3251.0 as well as on Stable#62.0.3202.75. Let me try to see if i can get the chromium change that has fixed this issue.

As per the repro case in c#15, i do not see this issue on any of the latest release channels (Canary, Dev, Beta & Stable). I am marking this as 'WontFix' and please feel free to update if someone still sees this issue.

PS: Issue is reproducible on M61#61.0.3163.100 & M63#63.0.3219.0.

Thank you!

The issue seems to be fixed with the 62.0.3202.75 update !

Per #27, this was reproducible in 63. We should make sure whatever fixed this in 62/64 is also present in 63. manoranjanr@, if you're able to bisect this on a local machine, can you try to determine what fixed this between 63 and 64, so we can merge the fix to 63?

Thanks!

#29: Eric, it doesn't repro on Latest Beta#63.0.3239.18. So we do not need any merge to M63.