Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Raspbian 10/buster, Chromium, 'Aw, snap!...'
105 views
Skip to first unread message
Robert Riches
Apr 3, 2022, 10:56:03 PM4/3/22
to
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.
--
Robert Riches
spamt...@jacob21819.net
(Yes, that is one of my email addresses.)
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.
--
Robert Riches
spamt...@jacob21819.net
(Yes, that is one of my email addresses.)
Theo
Apr 4, 2022, 5:15:47 AM4/4/22
to
Robert Riches <spamt...@jacob21819.net> wrote:
> 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?
As far as I can ascertain, Renderer Code Integrity enables Windows' Code
> 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?
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
Adrian Caspersz
Apr 4, 2022, 9:34:06 AM4/4/22
to
On 04/04/2022 03:56, Robert Riches wrote:
> 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."
>
That's a dumb down for something written in a log file.
> 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."
>
Have a look at the bottom of here.
https://support.zoom.us/hc/en-us/articles/360037195152-Sending-a-problem-report-and-client-logs
--
Adrian C
Theo
Apr 4, 2022, 10:34:12 AM4/4/22
to
Linux/arm to my knowledge). However you can enable logging in Chromium:
https://www.chromium.org/for-testers/enable-logging/
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
Robert Riches
Apr 4, 2022, 11:25:27 PM4/4/22
to
0 new messages