(title map viaWindows Latest)
In a post on the Chromium forum, Google andMicrosoftThe engineers are discussing this issue. The good news is that users can fix the bug shown above by adding the disable "RendererCodeIntegrity" function on the application startup parameters.
(1) Find a shortcut to Chrome Canary (or send it from the installation directory to your desktop);
(2) Right click on the shortcut to open ‘Properties’;
(3) In the target field, add the ‘--disable-features=RendererCodeIntegrity’ command parameter.
Once you've done this, click 'Apply.' Then double-click the desktop icon (shortcut) to launch the Chrome Canary browser normally.
It's worth noting that Microsoft Edge Canary and other Chromium-based browsers are not affected by this bug.