Issue metadata
Sign in to add a comment
|
Browser Tabs Crash Immediately when Remote Desktop Service is allowed to start
Reported by
karlmbu...@gmail.com,
Nov 14 2016
|
||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 Steps to reproduce the problem: 1. On Windows 7 SP1 machine, enable Remote Desktop (Control Panel > System > Remote Settings 2. Make sure that the Remote Desktop Services service is set to automatic or manual 3. Restart the computer 4. Start Chrome (54.0.2840.87 or newer) 5. Browser window will only show black screen, attempts to load other web pages just show the frown-face icon on tab top and continue to show just black screen What is the expected behavior? Should load the web pages as normal What went wrong? There seems to be an incompatibility with Chrome when the Remote Desktop Services service starts at startup. The issue doe not happen when the service is manually started, and the problem does not go away when it is manually stopped. Only happens when service starts as part of normal start-up, and can only be fixed by disabling the service and restarting machine. Have reproduced this on several different machines from different vendors Crashed report ID: no How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes I believe it worked on 54.0.2840.71 and older Chrome version: 54.0.2840.99 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Mar 6 2017
,
Mar 8 2017
Can we get a repro/bisect for this?
,
Mar 16 2017
I can't repro this in a Windows 7 SP1 VM using Chrome 57.0.2987.98 (Stable). After setting the "Remote Desktop Services" service to Automatic startup and restarting the VM, Chrome continues to work without any browser or renderer crashes. Original reporter: Can you check whether this is still a problem on the latest version of Chrome Stable?
,
Mar 16 2017
(Removing from stability sheriff queue until we can confirm this)
,
Apr 17 2017
No feedback was received in the last 30 days from reporter "karlmbundy@gmail.com", so archiving this. 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 manoranj...@chromium.org
, Nov 16 2016