This is a very fringe GPU setup. I don't know how we would possibly diagnose what's going on without debugging directly on a setup like this.

You might try the command line --ignore-gpu-blacklist , but it looks like the GPU process is failing to start completely when the dock is plugged in.

What exactly is DisplayLink?

I think SwiftShader or WARP would likely be the solution to this problem, but I don't expect many users to have this setup.

Sorry, I failed to mention that I did already try the flag #ignore-gpu-blacklist from chrome://flags. With that flag enabled webGL seems to load nicely. Attached is chrome://gpu with the flag enabled. But to me this seems another point, which indicates this is something that broke with Chrome update. Of course I cannot be sure, since I do not know where to get chrome update history and driver update history from anywhere, but I am quite sure that when I noticed chrome stopped working, it had just been updated to the version 54. I think I noticed the issue on 20.10.2016 (based on some chat history) and that's when I already had the chrome updated to version 54.0.2840.59 m (64-bit).

DisplayLink: http://www.displaylink.com/

I have: "Dell USB 4K Ultra Docking Station with Triple Video (D3100)", to be exact and basically it is a USB3 docking station with display outputs.

Deleted: gpu_html_with_display_link_ignore_gpu_blacklist_enabled.html 260 KB

gpu_html_with_display_link_ignore_gpu_blacklist_enabled.html 260 KB View Download

I had the same error.
Not with DisplayLink BUt with a combination of Chrome V 54.0.2840.71 m (64-bit)
and a Nvidia 9500GS.
I tried:
- all activating/deactivating Stuff in Chrome Settings; chrome://flags... (no change)
- newest and older Driver for Nvidia Graphic Card (no change)
- Fresh and clean Install of OS Win10 Pro 64Bit (no change)
- swap Graphic Cards from my second PC which has WebGL support and this one (unfortunately the same Brand_Nvidia) (but no change)
------->the Graphic Card from second PC is also a Nvidia Card. Works on 2nd PC but didn´t work on 1st PC?

I solved the isue by changing my Nvidia Card to a Sapphire Radeon R7 240

Now WebGL works like it should.

i too have been having the same problem for almost 3 weeks. the people at Google are NO help. webgl works on every other browser, edge, ie, firefox, and safari just not on the latest version of chrome. problem is the website i use everyday for work was designed around chrome and none of the other browsers function properly. 
i actually got someone from chrome on the phone and sent me on a wild goose chase for 2 hrs being transferred from department to department, then they sent me to hp, after being bounced around at HP for 2 hours they said its a chrome issue and they don't even know why google sent me to them to begin with.
all I've seen is Edward posting the same solution that doesn't work for anyone, as the solution.

can google at least provide us with version 53 that actually works so we can get back to work!

i had the same issue with webgl not working even though it was enabled with hardware acceleration. My issue was somewhat resolved simply by disabling hardware acceleration. I mainly needed webGL to play browser games and the games are now playable but they lag alot and are very slow to respond in some cases so apparently the new version of chrome (54) breaks the hardware acceleration somehow. hope this helps someone.

For me the problem is the same as in the first report. WebGL is disabled in Chrome, when I connect the monitor through USB3 with Display Link (however in works in other Browsers). If I connect it directly to computer via HDMI then it works. I attached the chrome://gpu reports with or without the display link connection.

Chrome 54.0.2840.71 m (64-bit)
Microsoft Windows 10 Pro

Computer: 
Dell Precision M3800
Intel(R) Core(TM) i7-4702HQ CPU @ 2.20GHz, 2201 Mhz, 4 Core(s), 8 Logical Processor(s)
16 GB RAM
NVIDIA Quadro K1100M
Intel(R) HD Graphics 4600
USB dock Display Link Targus ACP71EU

One workaround was to enable overriding the software rendering list in chrome://flags.

Deleted: chrome_gpu_no_display_link.html 151 KB

chrome_gpu_no_display_link.html 151 KB View Download

Deleted: chrome_gpu_with_display_link.html 46.9 KB

chrome_gpu_with_display_link.html 46.9 KB View Download

For this kind of issue with specific hardware, it's a bit hard to repro and fix for Chrome developers. 
However, this case looks like a regression, if you want to pay some efforts to root cause the issue, you may have a try with Chrome bisect tool. 
Just follow the instructions at https://www.chromium.org/developers/bisect-builds-py, and it shouldn't take a long time (within an hour if your network is fast) to find the commit that introduced the issue. Good luck!

You could also buy a display link device and see if you are able to reproduce the issue. Spending hours for finding your regression is unfortunately something I cannot do right now.

I notified display link support about this bug and this is the answer I got:

> Hi
> 
> This looks like the known issue which is covered by the article below:
> OpenGL 1.1 Reported Instead of 4.x
> DisplayLink adapter is not a graphics processing unit (GPU), therefore DisplayLink does not compute graphics and the notion of OpenGL support does not apply to it. We have flagged an issue in the Windows operating system which means OpenGL applications will use the GDI Generic (No Acceleration) renderer instead of the OpenGL 4.x renderer from the graphics card when the DisplayLink device is selected as main display. Until the operating system is fixed, please use the primary graphics card as main display.
> 
> Best regards,
> 
> Wim
> DisplayLink Technical Support

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

It sounds like this is a bug on DisplayLink's end, reporting the wrong OpenGL version.

If you think this is a bug in Chrome that has regressed then please run the bisect script on your hardware linked in comment #10.  I'm happy to help you with any questions you might have.  It's really fast to do and is the fastest way to help get this resolved.

There is no valid updates happened in the last few months, closing the issue. Feel free to reopen if needed.