Latest Chrome Canary build crashes with ‘Aw, snap' error, but there's a workaround

Following an update to Chrome Canary version 78.0.3874.0, upon launching the browser, users are presented with an 'Aw, Snap' error when trying to load any website, including About Chrome, and any settings pages such as Extensions and Plugins. Versions 78.0.3873.0 and older are unaffected by the bug.

A workaround was discovered to fix the ‘Aw, snap’ error:

  1. Pin Chrome Canary shortcut to the desktop.
  2. Right-click the shortcut and open Properties.
  3. In the target field, add the following command line:
    --disable-features=RendererCodeIntegrity

In a thread on the Chromium support website, Google and Microsoft engineers are discussing the problem, which is still open and is also where the above workaround was posted. Initial reports from the thread suggest that the browser is conflicting with another dynamic-link library (.dll) on Windows systems, with users being asked to post the list of dll's shown in chrome://conflicts, but as of writing the source of the problem doesn't seem to be clear.

Users stuck on the 78.0.3874.0 Canary build will need to go to the official Canary dev site to manually update to 78.0.3874.3, which fixes the problem since the auto update feature does not work in the bugged version.

Source: Chromium bugs reporting via WindowsLatest

Report a problem with article
1562437239_wallpaper-1920x1080
Next Article

Debian 10.1 scheduled for September release, later than usual for first point release

1559489516_huawei
Previous Article

Hongmeng OS could debut this week, power Huawei smartphones by year end

4 Comments - Add comment

Advertisement