jbauman, I would like to modify CollectGpuID to look for that string and enable acceleration in that case, even if DeviceID is empty.

Are you ok with such a workaround? If so, I'll prepare the CL and send it your way.

Thanks.

One problem is that maybe the GPU being used should actually be blacklisted, but we have no way of knowing. Also it's unclear to me how Chrome's performance changes when using software vs. the GPU on citrix.

So the idea here was to enable acceleration when in a remote session and let the VM take care of either passing them through or emulating them, depending on the setup. 

That being said, that will probably be suboptimal in case the hardware acceleration is not enabled in the session. So I'm looking at figuring out on how we can detect that and only enable acceleration if it makes sense.

I'll update the thread once I have more info.

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

commit e7b6ddf8b2940d17dc8dd0feaffce5b33ecee785
Author: georgesak <georgesak@chromium.org>
Date: Thu Feb 23 17:37:29 2017

Add workaround for GPU detection inside a Citrix remote session.

This CL extends the workaround to Citrix sessions (previously only pure RDP sessions were considered).

Note: I've tested this manually in our lab environment.

BUG= 681063 
TBR=zmo@chromium.org

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

[modify] https://crrev.com/e7b6ddf8b2940d17dc8dd0feaffce5b33ecee785/gpu/config/gpu_info_collector_win.cc

 Issue 161476  has been merged into this issue.