Still getting "Aw, Snap" crashes in Chrome on 2.18.4

[MaxStr]

A number of our users have been getting the "Aw, Snap" crashes in Chrome on Windows 10. The last time this was happening, the issue had gone away after updating to 2.18.4, but now it's happening again. We are on the latest Chrome version 83, (on Horizon 7.12).

Update: Disabling Chrome's "renderer code integrity" may have resolved the issue. I added this registry key to the affected VDI's, and (so far) haven't see the issue re-occur.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]

"RendererCodeIntegrityEnabled"=dword:00000000

Message was edited by: Max Strzelecki

[antonpaloka]

Is Chrome installed on an AppVolume? Do you let chrome AutoUpdate in your company policies?

[Natestack]

We having the same issue but we stayed on Appvol 2.18.2.

Will dont allow Chrome Autoupdate.

[MaxStr]

No, Chrome isn't installed on an AppVolume, it's installed on the gold image. Yes, we have Chrome auto-update enabled.

[robsisk1972]

I had the same problem a while back.  In my case, I installed Chrome on the master.   However, while creating another app stack on the provisioning machine, Chrome auto updated into that volume.   When I deployed the volume, it created the "Aw Snap" error due to a side by side installation.   Can't say that is the case in your situation but worth a look.

[sumanthT]

We've same problem in the VDI pool google chrome crashes & error was coming in "Aw Swap!"