Google Chrome Canary is a testing browser that permits Google to check out new options publicly earlier than deciding on whether or not to promote them to the extra steady builds or to quit on them both quickly or for ever.
Because it’s an experimental launch, Canary doesn’t at all times include the most steady enhancements, and generally testers find yourself not having the ability to use the browser in any respect.
This is what occurred after an replace launched by Google a number of hours in the past, as Chrome Canary finally ends up being caught with an “Aw, Snap!” error simply after launch.
In different phrases, in the event you set up Google Chrome Canary 78.0.3874.Zero in your gadget, the browser may simply return this error, not solely when making an attempt to load a web site, however just about when opening a brand new web page, together with from the settings display screen.
At first look, it appears like the replace of the browser is damaged, and WL got here throughout a dialogue on the Chromium bugs web page the place engineers talk about what precisely went improper in this launch.
“Yes, https://chromium-review.googlesource.com/c/chromium/src/+/1629607 blocks injection to Chrome renderer processes. No product should ever need to inject into Chrome renderers, but we are aware that some are still doing it,” an engineer explains.
At first it was believed that the situation is attributable to a compatibility downside with safety software program, like Windows Defender, or sure Windows 10 model, however the Google Chrome crew managed to monitor the bug down and begin engaged on a repair. At the time of writing this text, the botched replace is now not provided to customers through the built-in system.
If your gadget has already been up to date to Google Chrome Canary 78.0.3874.0, you need to set up the older model that doesn’t fail to load pages, or you should use the trick right here to skip the bug.
So mainly what you want to do is to launch Google Chrome Canary with a particular parameter that may permit you to bypass the bug and disable the characteristic that’s inflicting the block.
To do that, you want to create a desktop shortcut for Google Chrome Canary after which edit its properties:
Right-click Chrome shortcut Properties Target
In the goal discipline, you want to enter the following code proper after the present line:
So you goal discipline ought to appear like this:
“Google Chrome Canary exe location --disable-features=RendererCodeIntegrity”
Next time you launch the browser, every thing ought to work accurately with no error in anyway.
What’s vital to know is that Google Chrome Canary shouldn’t be used as the essential driver anyway, so bugs like this one shouldn’t have a huge impact on customers worldwide. As I mentioned, Chrome Canary is simply supposed to be a testing platform, so points often happen as a result of Google simply desires to see how some options work in their early implementations.
Google Chrome Canary is up to date daily, so if you’d like a extra steady expertise however nonetheless play with the new options that Google tries out, you need to go for…