Issue metadata
Sign in to add a comment
|
Chrome crashes on Citrix Xen upon launch as default browser from third-party app
Reported by
zjdo...@gmail.com,
Nov 28 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 Steps to reproduce the problem: 1. Install Chrome on Citrix XenApp server. Add the command-line options that allow Chrome to run on Citrix XenApp (--no-sandbox --disable-gpu). 2. User launches Chrome from the Start Menu for the first time and makes it his/her default browser when prompted. 3. Launching from the Start Menu on subsequent occurrences/days results in Chrome working as expected. 4. If Chrome is currently closed and the user clicks on a link from a third-party app (let's say Outlook in this case), Chrome will open because it is the default browser and will immediately crash. Any new tabs opened will also fail. What is the expected behavior? Clicking on a link inside of an app when Chrome is closed should cause Chrome to launch and display said link. What went wrong? Chrome will crash because when started from a third-party application, the command line options that are required for using it on a Citrix XenApp server do not pass-through. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? No Chrome version: 54.0.2840.99 Channel: stable OS Version: 6.1.7601 Flash Version: Shockwave Flash 23.0 r0 For some reason, a Chrome crash report is not created when this happens.
,
Nov 29 2016
This bug is a duplicate of crbug.com/627071 . Also please, PLEASE, never use the "--no-sandbox" flag in production environment. This flag is putting at risk not only the user but your server infrastructure as well when you are running a remote app from the server. The right flag you should use is --allow-no-sandbox-job. It might sound similar but these flags are worlds apart in terms of what they do.
,
Nov 29 2016
The usage of the "--no-sandbox" flag was put in place in our environment during the last week of October 2016. For background: We originally had Chrome on XenApp configured with the command line switches "--allow-no-sandbox-job --disable-gpu". However, on the morning of October 24, 2016, we began receiving reports of Chrome opening and then immediately crashing (in this case the crash did not leave the Chrome window visible--the entire process would fail). This only happened on one Xen server which we disabled for the day while we investigated. On Tuesday the same problem happened on another Xen server. On Wednesday while working on a fix we discovered a Google Forum posting the "--no-sandbox" flag which did present us with an error but was currently the only method in which we could get Chrome to open on Xen. We worked around the error by also adding a flag that disabled the error message. I have just searched again for this issue and found the Chromium ticket showing a fix has been rolled out for this issue. https://bugs.chromium.org/p/chromium/issues/detail?id=659026. I will be reversing those changes and utilizing the correct command line flags for a Citrix environment. This issue in this ticket (and its duplicates) still stand. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Nov 28 2016Components: Enterprise
Labels: Needs-Triage-M54 M-54