Remote Desktop Services Crashes 64 bit version
Reported by
nathan.m...@bdpint.com,
Feb 6 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Load RDS services on a Windows 2008 R2 server or later. 2. Install 64 bit version of Chrome 56. 3. Launch chrome, it opens but snaps and does not function. What is the expected behavior? For Chrome to function as a browser that enables you to, you know, navigate to web pages. What went wrong? It got the oh snap and you cannot navigate to any websites whatsoever. This has been consistent so far as the 64 bit version has existed. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? No Chrome version: 56.0.2924.87 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 24.0 r0 It's never worked and it's been reported before and yet nothing has been done about it.
,
Feb 6 2017
Remote Desktop Services (RDS) is different from Chromoting (based on the information from the bug). This appears to be a problem with the Chrome Browser working when RDS is installed, not a problem with Chrome Remote Desktop.
,
Feb 8 2017
nathan@ could you please provide the crash id from chrome://crash. If you are unable to get it, please provide the raw crash data. This will help us in debugging further. https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug
,
Dec 11 2017
Same bug. How to test. 0. We have Windows 2012 RDS server with full interactive access (not RemoteApp), UAC must be ON 1. Logon server 2. Start Chrome (it's must be ok) 3. Close Chrome 4. Start something to activate UAC prompt and select Yes or No for close it. 5. Start Chrome now (it's fail with crash error) If I use Program Compatibilty Assistant chrome start at last step, but dont work without it anyway. Workaround for me is using a params: --no-sandbox --no-infobox --disable-gpu after this chrome starts and work fine but show crash window at chrome://* pages Version 62.0.3202.94 (x64) stable Bussines (msi installer)
,
Dec 13 2017
,
Dec 13 2017
sry, right params is: --no-sandbox --disable-infobars --disable-gpu
,
Dec 13 2017
From the screenshot, it looks like Chrome is crashing, so I don't think this is related to Chromoting. The "Remote Desktop" mentioned is Microsoft's, not Chromoting. See also Joe's comment#2.
,
Dec 13 2017
yeah its not chrome remote desktop problem, it\s chrome problem istalled at RDS server
,
Dec 14
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ligim...@chromium.org
, Feb 6 2017Components: Services>Chromoting
Labels: M-56