Chromium

I believe that this might be related to the GPU acceleration. It seemed to be that Chrome process that crashed during my remote desktop session (the session on the console continued to work correctly).

I tried going to about:flags and setting
- "GPU compositing on all pages": Default -> Disabled
- "Disable accelerated 2D canvas": Disabled -> Enabled

This fixed the crashes, but the thing is... i then restored the default behavior and chrome isn't crashing anymore... even though it should have if those settings were at fault?

The following worked for me :

Based on what we have checked, the problem is related to Chrome and Windows Aero compatibility issue; you will need to disable Windows Aero on the Host computer ... On the Host computer's Console session, click on Windows Start -> Right-click My Computer -> Properties -> Advanced system settings -> Performance settings -> Under "Visual Effects" tab, untick the "Enable desktop composition".

[Comment Deleted]

https://crbug.com/chromium/165636#c2 fixed the problem for me.


https://crbug.com/chromium/165636#c3, the option to untick the "Enable desktop composition" is not available (Windows 7), but I did turn off all visual styling...but Chrome still crashed.

@ https://crbug.com/chromium/165636#c5 : You must directly logon the server and not trough RDP or other RDP software. Otherwise you can not see this option.
 

I just made the changes suggeted in https://crbug.com/chromium/165636#c2 from chrnosph and will report back if this fixes the RDP/Chrome issue once someone logs on locally to my PC.  

I have been experiencing this same issue for some time myself. I can confirm that it didn't use to be a problem, but started some time in the last year it seems, probably when some sort of graphics acceleration was introduced because the issue is clearly related to graphics rendering. It happens when two users are logged into the system at the same time (using the termserv.dll patch in Windows 7).

I have seen something similar occur in a couple of other programs besides Chrome, including Windows Live Mesh (R.I.P. :( ) and another Java program. In Windows Live Mesh the UI is simply rendered all white without any content, but the application still responds. The Java program, similar to Chrome, would completely stop responding and display a message to force close. It's only the UI that is not responsive as either logging out  or locking the console for the second user causes the application to instantly become responsive again (or draw the contents of the all white screen in the case of Mesh).

Another interesting scenario I've found: I use the computer I experience this on as an HTPC and have the desktop resolution set to 1280x720 to improve readability for text and apps from the couch, but when Windows Media Center opens, it switches to 1920x1080 (for optimal video quality). When I remote the computer in another account, the resolution varies for the session depending on the device, but typically 1280x768 or 1600x900. I experience the freezing no matter what the RDP client resolution is. I don't know that it has anything to do with the resolution so much, as more than likely it's just the full-screen nature that Windows Media Center runs in, but the apps that experience these symptoms, including Chrome, will also instantly become responsive when I open Windows Media Center on the user logged into the main console.

So my theory is it has something to do with the graphics rendering getting confused and not taking into account the multi-user sessions scenario and defaulting to sending some system callback to the console user instead of the remote user. In the case of a full-screen application running for the console user, this frees up the windowed context to be used exclusively by the remote user. I don't know anything about the details behind graphics rendering or the differences between windowed and full-screen contexts in Windows (only that I understand there's a difference), but it seems logical. I'm also unsure as to how much an application can do itself to workaround this issue or if the fault lies somewhere at the operating system or possibly graphics driver level. For what it's worth, my system has an ATI Radeon HD 4850 GPU.

Clearing the "Enable desktop composition" option worked for me. Thanks.

[Empty comment from Monorail migration]

My normal workaround for this is to open the taskmanager and disconnect the current active user (not log out) which in my case is normally my girlfriend's session that has been left active. But sometimes when she is still using the machine that is not an option.

#2 worked for me. Thanks a lot!

#3 did not try this, but I assume this would disable desktop composition generally in windows, which is not my intension as I also use the console normally ie not via RDP.

Never had the problem in firefox (or chrome at some point I cant remember), except for with homebanking which is because of the embedded java window. Windows live mail also has the problem with some of the controls, but not in outlook, so I'm now using that for my secondary hotmail stuff. Actually windows live mail still works, it does not crash like chrome, some of the controls are just white/invisible but actually still works if you know where to click :-) Media Player Classic crashes too.

Hrmf. Just found that this (for me) very useful chrome extension called pocket, still makes chrome crash when used even with the two flag options. It happens when you "pocket" something and the dialog slides in from the top. I use the extension a lot, so I will have to keep looking for another fix I guess.

Here is the extension:
https://chrome.google.com/webstore/detail/pocket-formerly-read-it-l/niloccemoadcdkdjlinkgdfekeahmflj

This started happening for me with 24 and had nothing to do with running multiple instances of chrome at the same time, even though I do run a concurrent RDP setup. As soon as I'd try to load ANY website when connected through remote desktop, chrome would instantly hang. I was able to roll back to version 23 and the problem went away, but I didn't want to live with chrome never updating. I updated to 24, the problem returned instantly but disabling "GPU compositing on all pages" per #2 seems to have completely fixed the problem.

@#17: about:flags only affects chrome, fb2k behaviour is unrelated. desktop composition only affects aero, it has nothing to do with dual monitors.

Sadly I am also experiencing the same issue.
However even after trying the suggestions in https://crbug.com/chromium/165636#c2 and #3 I am still suffering the same crashing when opening chrome in the RDP session.
"Google Chrome has stopped working"
Application version 25.0.1364.152 on Windows 7 Home Premium with RDP patch.
Any other thoughts.
Just a quick check, I assume everyone is logging in via RDP using a different username than the console?

Cheers.
flipdee

Good catch - I'm using the RDP patch, too. Normally I don't use the same user logged n the console, but that maybe the case sometimes.

I never use the same user that is logged into the console.
I even went to the extent to login as the "RDP" user on console and try the https://crbug.com/chromium/165636#c2 and 3 suggestions directly (Chrome works on console with this user).
No joy though.
Strangely enough I have a Windows 7 Professional installation where the Chrome within RDP doesn't crash!
Hmmm, patch to blame?

I'm using the same user as logged in via console, but I'm also using
2008r2, not win7

Ah, interesting.
Just checked another Windows 7 Enterprise install and chrome is fine on it's RDP session too.
I've also tried the MSI install on the offending Windows 7 install with no joy, as I was starting to think the user specifc chrome installs were causing the problem.
Have you tried logging in using another user on 2008r2 to see if you get the same problem?

I have another user permanently logged in, and the issue didn't reappear so
far after doing what I posted in #2 so... ^^

User A is my account I use via rdp/console depending on where I currently
am at.

User B is permanently logged in via console, never per rdp.

Well, wonderful. Latest update broke chrome for me even further. Now setting all acceleration flags to off doesn't help, nor disabling desktop composition. What are you doing, google. I guess I'll have to find a replacement browser for now.

[Comment Deleted]

#2 fixed it for me for the sites I use reguarly.
But on some other sites it still crashes.
Win7 Pro.

Thank you Mrldaho - works for me!

[Comment Deleted]

Unfortunately no luck for me. still crashes on opening.

Unbelievable! Chrome doesn't hanging! Thanks to Mrldaho, bless his soul!

Can a Chrome committer please comment on this issue?

Firefox has the same problem: https://bugzilla.mozilla.org/show_bug.cgi?id=594407

Chrome should automatically disable hardware acceleration under Remote Desktop and re-enable it for local sessions. See https://bugzilla.mozilla.org/show_bug.cgi?id=594407#c63 for a related discussion.

i also have this problem.  Sometimes need to RD in to check a few things and chrome will crash

happens on a pair of ncomputing L300 units I just set up. Will try #3 tomorrow. Definitely seems to be tied to hardware.

#2 - yup Disabling Hardware Acceleration seems to work around this

Recently I changed videocard, but problem persists. Maybe something with motherboard drivers? I have ASUS p8z68

This has nothing to do with your hardware. It only has to do with hardware acceleration being enabled. This is a software configuration issue, not a hardware problem.

@cow: Other video drivers also have been installed.

About FireFox: it also has the problem, but it appears only during launching. After that it works without any problems. But Chrome hangs after launching during navigation between web-sites.

I have the same behavior with Firefox and Chrome. It doesn't matter if I launch a new browser or attempt to use an existing one, the window hangs.

Anyway, none of this really matters because it doesn't look like anyone from Google is looking at this issue yet (status is still "unconfirmed").

I applied the trick from MrIdaho, that one worked :)

Tried Mr.Idaho's solution (almost said potato, lol!) but it was unsuccessful. I'm using RDP for simultaneous users with chrome installed in the Program Files (x86) folder. I read another topic @ https://productforums.google.com/forum/#!topic/chrome/XmFyHTT166w
that the following switch as a suggestion: --disable-background-mode

And that showed some promise as my session on chrome lasted all of 2 minutes. I would get pixelization/graphic rendering quirks on the Google web store but it didn't crash there like it previously did. But it finally crashed when I went to youtube :-(

matthew@, Can you please confirm us are you still seeing this issue with Latest Chrome as well?

Thanks in advance.

This issue still occurs for me under Version 30.0.1599.69 m using the following repro steps:

1. User 1 logs into Windows 7 using Remote Desktop, and opens Chrome.
2. User 2 logs into the same system locally
3. The second User 2 logs in (step #2) the browser belonging to User 1 (step #1) will crash.

I can confirm that this is still a problem with 30.0.1599.69 m

Disabling GPU solved it for me on the 30.x version.   Disabling composition on the RDP connection had no effect.   Using chrome in multi windows user environment.

I have also noticed that minimizing the RDP session would actually render the tabs in chrome. Otherwise it would be stalled.   So you could technically switch to a tab, minimize RDP, then work on that tab after you maximized it. as long as it didn't popup any new windows.

This started happening to me again once I upgraded to 30 when on earlier versions the disabling GPU compositing had fixed it. MrIdaho's fix worked for me and everything is back to normal again.

It would be really great help if someone can answer few questions/experiments:-

1. what is machine hardware configuration ?
2. is there any anti-virus installed ? (what is that?)
3. is your machine in power saving mode ? (or any specific configuration)
4. can you reproduce the issue with new user profile (chrome://settings/createProfile)
5. open just incognito window and use and see if this freezes ?
6. have you installed any extension recently which started causing the issue ?
7. can you attach these info when freeze/crash occurs:-


> attach minidump:- http://www.chromium.org/for-testers/bug-reporting-guidelines/hanging-tabs

 >chrome://gpu
 > chrome://conflicts/
 > chrome://tracing/ [record tracing when chrome hung and attach via file uploader or google drive; file is large]

Thanks in advance.

[Comment Deleted]

If, like me, MrIdaho's fix in #28 worked for you, but whenever you don't have chrome open and another application attempts to launch your default browser the flags aren't set, I have a workaround for you.

In RegEdit, go to "HKLM\SOFTWARE\Classes\ChromeHTML\shell\open\command" and edit the string value so that instead of reading:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -- "%1"

it reads:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-no-sandbox-job --disable-gpu --disable-flash-sandbox "%1"

The flags are NOT put in quotes, and you must remove the "--" before "%1" otherwise it won't work correctly. You can verify that everything is working properly by leaving the chrome://gpu/ URL open and making sure that hardware acceleration unavailable is set for all the values.

If this bug ever gets fixed you will of course have to update that registry key to get hardware acceleration again, but until then, it's a more comprehensive fix.

Does 32 cause the browser to hang like it used to before the flags, or do the videos just not work? I can live with the latter, the former would be a deal breaker.

what I've been doing since May 2013, is using a shortcut on the desktop to chrome.exe using the switch --disable-accelerated-compositing

remote in... see that chrome is blank/transparent/crashed... kill the process tree... launch my custom shortcut!

something in a recent update must have broken this?

oh well... i just switched to the next tab from my search... and found the switch --disable-gpu. well what do ya know? it worked. Still, something has changed that my shortcut quit working recently.

#28's fix was working. But seems to have stopped with version 34.0.1847.131 m.

Error still persists with Version 37.0.2041.4 m.

#28 worked for me too, thanks a lot!

I have experienced the problem. But some time ago I found that my chrome only hangs when another one user is logged on the computer at the same time. When I kill process dwm.exe of other user - all starts to work excellent.

MrIdaho, thanks so much for your workaround in https://crbug.com/chromium/165636#c28.  It's working for me on Version 36.0.1985.125 m.  I hadn't been able to use Chrome for months due to this bug.  It happens to me because my PC is multi-user.  My PC primarily acts as a server, so it's on full time, and there's always a user logged in locally on the console.  But, when I'm at work, I am always logged into it remotely via RDP.  I couldn't use Chrome any more because of the frequent crashes due to the RDP bug.  Now, I can again thanks to MrIdaho.

(Automated-archive) Crash report hasn't been modified in more than one year, please re-open if this is still an issue.

still happens on 51.0.2704.106

Same problem on 58.0.3029.110 (64-bit) on Windows 10 (latest versions)
Crome crashing on some sites.

This issue was migrated from crbug.com/chromium/165636?no_tracker_redirect=1