Latest Google Chrome released for Windows

Latest version 92.0.4512.4 crashes and deletes extensions in Mint Cinnamon. Anyone having this issue in Windows? Not Kernel related.

MikeMecanic said:

Latest version 92.0.4512.4 crashes and deletes extensions in Mint Cinnamon. Anyone having this issue in Windows? Not Kernel related.

Lot's of reported problems in the last day or so. All over Reddit, Google Product Forums, here...

All seems a bit weird. I wouldn't be surprised if this time Google aren't to blame. Could just as easily be an Antivirus Software in common use that has flagged some essential Chrome files as harmful and Quarentined them.

Our security setup (not too high) in Mint resists to Chrome-dev update in the guess account (95.0.4512.4 only). The admin account is not used (never seen the Web) and it has no wired connection to kill cross-talk, to minimize incoming malicious script(s) from running. Plus, the browser was never opened in the admin account (my error).

Offline, the terminal overwrites the previous package (92.0.4503.0-1) and the browser opens normally in the admin account. The new package remains corrupted in the Guess account and unusable. We made that discovery by reading about the error code that defines the bug we have pretty well, SIGSEGV error code implies a memory access violation.

The latest package won't install on the guess account at all, while the previous one did in update manager. We also have similuar issues on the standard account in Windows 10 for some apps, Radeon is among them.

Code:

dpkg -l | grep google-chrome-unstable
ii  google-chrome-unstable                                     92.0.4512.4-1                              amd64        The web browser from Google

This website host previous builds:
google-chrome packages dissection - Repology


Opening chrome as guess from the terminal:

Code:

 google-chrome-unstable 
[8397:8397:0522/120728.546580:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is swiftshader
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0330
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0330
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0330
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0330
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0330
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0330

6 days to get the correction. The Dev channel is back to normal.

It's always done that for me.