Google Chrome Unresponsive on Terminal Server / Citrix XenApp

Like posted before I’m distributing icons from the Windows Group Policy. Citrix has posted a CTX article about this issue, as from version 24 Google Chrome becomes unresponsive and will freeze a lot when you don’t have a GPU. As the article states it’s due it uses the Microsoft RemoteApp technology: http://support.citrix.com/article/CTX132057



I’m seeing these issues too as I publish Google Chrome from the XenApp desktop; Google Chrome will freeze, high memory and CPU usage, corrupted profiles and processes being helt active even after killing the whole chrome.exe process.

Looking into Google Chrome and their forum it seems that Google Chrome is very unstable from version 36 in general, a lot of people are complainting about issues like mentioned above. So what if I use the methods for solving these issues from the Citrix CTX article? Will it help?

When distributing icons through the policy you can use these Chromium flags (http://peter.sh/experiments/chromium-command-line-switches/) for disabling the GPU, disabling PepperFlash and disabling the sandbox.

The command you can give within the icon shall be:

--allow-no-sandbox-job --disable-gpu --disable-bundled-ppapi-flash

Great, when a user is entering the XenApp desktop and opens Google Chrome you’ll see Google Chrome is opening with these flags, also the performance will be better on the Citrix server. Nice job….. BUT…… what if a user opens a new window from within Google Chrome? The flags are not being used, just because it opens the new Google Chrome window without the flags:

If you open the taskmanager you’ll see Google Chrome being opened from the icon with the correct flags, but also that the user opened a few new windows from Google Chrome and have the flags —type=gpu-process:



Now I sorted out a few registry keys which you can import (.XML) so all the Google Chrome sessions will open all with the flags mentioned above. Also the Google Chrome will be the default browser in the XenApp desktop:



<Collection clsid="{53B533F5-224C-47e3-B01B-CA3B3F3FF4BF}" name="Google Chrome Default Browser" changed="2015-03-03 13:56:19" uid="{5295C641-B1D3-46ED-B1E5-8D80C813AA87}" disabled="0" userContext="1" bypassErrors="1"><Filters><FilterGroup bool="AND" not="0" name="Groupname" sid="S-1-5-21-2147495179-3017276484-3716729273-24238" userContext="1" primaryGroup="0" localGroup="0"/></Filters><Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="DefaultIcon" status="(Default)" image="7" changed="2015-01-20 08:20:32" uid="{64FE3A12-DDE5-4945-B7FE-309F303E9B3F}"><Properties action="U" displayDecimal="0" default="1" hive="HKEY_CURRENT_USER" key="Software\Classes\http\DefaultIcon" name="" type="REG_SZ" value="D:\\Program Files (x86)\\Google Chrome\\chrome.exe,0"/></Registry>
    <Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="command" status="(Default)" image="7" changed="2015-02-05 10:07:33" uid="{F3C1DE00-52BD-460B-BAC7-C80C9C50FAEF}"><Properties action="U" displayDecimal="0" default="1" hive="HKEY_CURRENT_USER" key="Software\Classes\http\shell\open\command" name="" type="REG_SZ" value="&quot;D:\Program Files (x86)\Google Chrome\chrome.exe&quot; --disable-gpu --allow-no-sandbox-job --disable-bundled-ppapi-flash %1"/></Registry>
    <Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="DefaultIcon" status="(Default)" image="7" changed="2015-01-20 08:20:49" uid="{E5BBADDF-E726-4360-AA2F-11D23CFE4CCF}"><Properties action="U" displayDecimal="0" default="1" hive="HKEY_CURRENT_USER" key="Software\Classes\https\DefaultIcon" name="" type="REG_SZ" value="D:\\Program Files (x86)\\Google Chrome\\chrome.exe,0"/></Registry>
    <Registry clsid="{9CD4B2F4-923D-47f5-A062-E897DD1DAD50}" name="command" status="(Default)" image="7" changed="2015-02-05 10:06:56" uid="{71F814F1-7115-46BE-9123-B4A6262A5670}"><Properties action="U" displayDecimal="0" default="1" hive="HKEY_CURRENT_USER" key="Software\Classes\https\shell\open\command" name="" type="REG_SZ" value="&quot;D:\Program Files (x86)\Google Chrome\chrome.exe&quot; --disable-gpu --allow-no-sandbox-job --disable-bundled-ppapi-flash %1"/></Registry>
</Collection>

Right, and now? You’ll see no more —type=gpu-process enabled chrome.exe processes:



Comments