UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Create a large screen using Xvfb:
Xvfb :7 -screen 0 1920x9000x24 -fbdir /tmp/vf
2. Connect to it using x11vnc to see what is going on
x11vnc -display :7 -localhost
vncviewer localhost:5900
3. Run chromium inside this session, with the big screen resolution
DISPLAY=:7 tools/chrome/chrome --window-size=1920,9000 --window-position=0,0 --user-data-dir=/tmp/tmdpdir
4. Navigate to http://www.euronews.com/ in the just opened chromium
5. Take a screenshot of the framebuffer Xvfb created
DISPLAY=:7 import -window root -quality 90 /tmp/shotscreen.jpg

What is the expected behavior?
For the webpage to be rendered properly

What went wrong?
On the screenshot you will see rendering errors, seen as black boxes.
I've tried several options to resolve this, using the stable chrome version for arch, using the --no-gpu flag, resizing the window only after the webpage loaded, non of which worked for me.
I've also tried to play with the website I've mentioned to understand what causes this behavior, but did not find anything yet.
Also note, that this behavior is not only seen in the screenshot, you can scroll down the VNC desktop you are connected to to see the rest of chromium (unless you have a really really big screen :P), and you will see the artifacts.

Did this work before? N/A 

Chrome version: 58.0.3005.0  Channel: dev
OS Version: Linux michx 4.9.8-1-ARCH #1 SMP PREEMPT Mon Feb 6 12:59:40 CET 2017 x86_64 GNU/Linux
Flash Version: Disabled

P.S. I have no affiliation with the website I've mentioned, it's just the only one I've found to cause those problems, there are probably more like it.

 

Deleted: renderbug.png 4.5 MB

	renderbug.png 4.5 MB View Download