[ISSUE] Constant "Aw, snap!" in Chromium on musl

[ISSUE] Constant "Aw, snap!" in Chromium on musl

[Logarithmus]

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

New issue by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/issues/29654

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* package:  `chromium`
*affected package(s) including the version*: latest version of `chromium` from the tier 1 repo

### Expected behavior

Normal operation

### Actual behavior

Aw, snap! Error 256 appears and the tab dies.

### Steps to reproduce the behavior

Open Chromium and browse the Internet for some time, especially JS-heavy websites like YouTube or Facebook.

Re: Constant "Aw, snap!" in Chromium on musl

[fosslinux]

[-- Attachment #1: Type: text/plain, Size: 211 bytes --]

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-804715681

Comment:
Can reproduce. Not consistently though. Likely relation to #29105.

Re: Constant "Aw, snap!" in Chromium on musl

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1121783335

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: Constant "Aw, snap!" in Chromium on musl

[fosslinux]

[-- Attachment #1: Type: text/plain, Size: 155 bytes --]

New comment by fosslinux on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1122009488

Comment:
not fixed

Re: Constant "Aw, snap!" in Chromium on musl

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1208832551

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: Constant "Aw, snap!" in Chromium on musl

[Logarithmus]

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]

New comment by Logarithmus on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1208970260

Comment:
Bump

Re: Constant "Aw, snap!" in Chromium on musl

[ohoes]

[-- Attachment #1: Type: text/plain, Size: 440 bytes --]

New comment by ohoes on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1874597139

Comment:
Seems to have to do with the fact that sandboxed chromium uses features that are missing in musl. If you run chromium with "--no-sandbox" option, i.e. without sandbox mode, then the problem is not present. I can't believe that after all these years this still hasn't been fixed. Very disappointing.

Re: Constant "Aw, snap!" in Chromium on musl

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 384 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1874718291

Comment:
Its not that simple, `--no-sandbox` has a bunch of implications other than the simple filtering of system calls, the issues are most likely related to multi threading and locks/mutexes, `--no-sandbox` makes chrome basically single threaded.

Re: Constant "Aw, snap!" in Chromium on musl

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1874718291

Comment:
Its not that simple, `--no-sandbox` has a bunch of implications other than the simple filtering of system calls, the issues are most likely related to multi threading and locks/mutexes, `--no-sandbox` makes chromium basically single threaded.

Re: Constant "Aw, snap!" in Chromium on musl

[ohoes]

[-- Attachment #1: Type: text/plain, Size: 587 bytes --]

New comment by ohoes on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1879172442

Comment:
> Its not that simple, `--no-sandbox` has a bunch of implications other than the simple filtering of system calls, the issues are most likely related to multi threading and locks/mutexes, `--no-sandbox` makes chromium basically single threaded.

Still, running without sandbox is the only workaround (that I know of), though. Perhaps it would be useful to add it to the package. Without that argument, Chromium is practically unusable on musl.

Re: Constant "Aw, snap!" in Chromium on musl

[Duncaen]

[-- Attachment #1: Type: text/plain, Size: 222 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1879196587

Comment:
You should not be using chromium without the sandbox though, yes its unusable.

Re: Constant "Aw, snap!" in Chromium on musl

[klardotsh]

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

New comment by klardotsh on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-1951431191

Comment:
Chromium here is so far beyond broken as to be comical, and this seems to be a somewhat recent regression.

- Constant tab deaths as described in OP
- Constant infinite-loading-spinner states when navigating between pages
- Generally hangs when trying to kill tabs stuck in ^ state
- Occasional full browser locks

This happens with or without sandbox flags, with GTK 3 or 4 (set by CLI flags), with X11 or Wayland Ozone hints, and seemingly no matter what.

Unfortunately some of the above appears to be Blink related and not Chromium-specific, as the same freezing happens with Qutebrowser. Functionally, this means I have to use a glibc-based Distrobox container to run Chromium-ish browsers for that 5-10% of the internet too lazy to check their work in Firefox, because nothing Chromium-based currently works on my musl-based install.

Re: Constant "Aw, snap!" in Chromium on musl

[ohoes]

[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]

New comment by ohoes on void-packages repository

https://github.com/void-linux/void-packages/issues/29654#issuecomment-2016775731

Comment:
> Chromium here is so far beyond broken as to be comical, and this seems to be a somewhat recent regression.
> 
>     * Constant tab deaths as described in OP
> 
>     * Constant infinite-loading-spinner states when navigating between pages
> 
>     * Generally hangs when trying to kill tabs stuck in ^ state
> 
>     * Occasional full browser locks
> 
> 
> This happens with or without sandbox flags, with GTK 3 or 4 (set by CLI flags), with X11 or Wayland Ozone hints, and seemingly no matter what.
> 
> Unfortunately some of the above appears to be Blink related and not Chromium-specific, as the same freezing happens with Qutebrowser. Functionally, this means I have to use a glibc-based Distrobox container to run Chromium-ish browsers for that 5-10% of the internet too lazy to check their work in Firefox, because nothing Chromium-based currently works on my musl-based install.

Actually, I now use chromium with jitless js flags, and it works almost flawlessly (for me) crazy enough. Took me a darn long time to get this working on musl. I found it at the ungoogled chromium repo. Let me know if it works for you, too. 
https://github.com/DAINRA/ungoogled-chromium-void?tab=readme-ov-file#musl-crashes-mitigation)