子豚のココのお勧め商品　joyeux cochonnet

"It appears the problem only affected 64-bit versions of Windows, and it's not clear how many people have experienced the issue. The simple solution to getting Chrome up and running again is to use the --no-sandbox flag. This is not something that is normally recommended, as it brings Chrome processes out of their protected, sandboxed state, but as a temporary measure -- and to avoid having to switch browsers for too long -- it's fine.

Right click on the desktop shortcut to Chrome and select Properties.
Move to the Shortcut tab and click in the Target field.
Type a space at the end of the path that appears in the field followed by --no-sandbox.
Hit OK, and use the shortcut to launch Chrome.

You'll notice an information bar at the top of the screen that reads "You are using an unsupported command-line flag: --no-sandbox. Stability and security will suffer" but Chrome will at least be working once again."

Looks like this is reversible once Google releases an update to fix this crashing issue by simply going back into the shortcut properties for Chrome on your desktop and remove " --nosandbox"

I'm going to closing this out for comments, since the specific issue here is fixed and there will be no future work on this bug. For the small number of people asking why Chrome checks signatures on the 64-bit syscall stubs, it's because doing so significantly mitigates issues from third-party software hooking inside Chrome's sandboxed processes. Whereas on 32-bit Windows we're forced to use much more permissive hooking, and as a result we see far more issues due to malfunctioning third-party software such as AV or other utilities that: break ASLR, leak privileged objects, or just introduce general instability that leads to very high crash rates inside our sandboxed processes.

We will continue to track the impact of our 64-bit syscall stub validation, and if we see significant conflicts in the future we can revisit our decision. But for now, our crash report data supports the position that the strict validation is providing a real end-user benefit in terms of stability and security.