Raspbian 10/buster, Chromium, 'Aw, snap!...'

Apr 04, 2022 Last reply: 4 years ago 4 Replies
R

While trying to get Zoom in a browser working (with Raspbian



10/buster and Chromium 92.0.4515.98 or perhaps newer by now on a Raspberry Pi 4 with 4G RAM), I often get "Aw, snap! Something went wrong."

Web searching found one suggested solution is to use a



--disable-features=RendererCodeIntegrity option. However, some hits on that topic claim that solution is Windows-specific.



Is that option (--disable-features=RendererCodeIntegrity) specific to Windows? Or, is it also applicable to Linux, Raspbian to be specific?



Thanks.


Vote
Twitter Facebook LinkedIn
T

As far as I can ascertain, Renderer Code Integrity enables Windows' Code Integrity Protection feature, to prevents unsigned DLLs from linking against Chrome's renderer process.

Linux doesn't have the same feature, so I don't think that solution is applicable to Linux.

Theo

Vote
Twitter Facebook LinkedIn
A

That's a dumb down for something written in a log file.

Have a look at the bottom of here.

formatting link

Vote
Twitter Facebook LinkedIn
T

The OP is using Zoom in a browser, not the Zoom app (which doesn't exist for Linux/arm to my knowledge). However you can enable logging in Chromium:

formatting link
The 'Aw, snap!' message suggests the renderer process crashed. That's the bit that reads the web page and does the page layout. *Something* in it has gone wrong, but it's a very broad scope so no clues what it might be. The log might help.

Theo

Vote
Twitter Facebook LinkedIn
R

Thanks for that pointer about enabling Chromium logs!

Vote
Twitter Facebook LinkedIn

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required