diff options
| author | joshia@google.com <joshia@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-14 23:42:06 +0000 |
|---|---|---|
| committer | joshia@google.com <joshia@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-14 23:42:06 +0000 |
| commit | e042db5288480d9ca61b155d8b8fa9ea42481554 (patch) | |
| tree | 9f562038ef3b9f27e9abe341f8964f5f5c9a0d7e /views/window/window.h | |
| parent | 8425e75f99be6b2d31418ffdeee088023d4580c1 (diff) | |
| download | chromium_src-e042db5288480d9ca61b155d8b8fa9ea42481554.zip chromium_src-e042db5288480d9ca61b155d8b8fa9ea42481554.tar.gz chromium_src-e042db5288480d9ca61b155d8b8fa9ea42481554.tar.bz2 | |
Revert 77345 - Speculative fix for Chrome launch issues in Citrix environment.
Reverting since Further debugging proved that this is not relevant
at all.
Several bugs and user fourm threads like:
https://groups.google.com/group/google-chrome-frame/browse_thread/thread/9aa7c3296861a2cd?pli=1
point to Chrome startup issues with Citrix. Based on the
user feedback, it appears that browser process is hung trying
to launch renderer that comes briefly and exits. Further
investigation revealed 3 DLLs that get injected in every
process in Citrix environment.
This speculative fix adds those DLLs to the problem DLL list
for sandbox.
BUG=2423,63195,55875
TEST=run chrome or Chrome Frame via citrix published app shortcut.
Review URL: http://codereview.chromium.org/6623064
TBR=joshia@google.com
Review URL: http://codereview.chromium.org/6694006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@78126 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'views/window/window.h')
0 files changed, 0 insertions, 0 deletions