Message-ID:

21 May, 2024: Computers section is temporarily disabled for maintenance. It will take several days before it's back.

computers / comp.sys.raspberry-pi / Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'

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

<slrnt4kni1.ohv.spamtrap42@one.localnet>

https://www.rocksolidbbs.com/computers/article-flat.php?id=4513&group=comp.sys.raspberry-pi#4513

copy link Newsgroups: comp.sys.raspberry-pi

Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: spamtrap42@jacob21819.net (Robert Riches)
Newsgroups: comp.sys.raspberry-pi
Subject: Raspbian 10/buster, Chromium, 'Aw, snap!...'
Date: 4 Apr 2022 02:56:01 GMT
Organization: none-at-all
Lines: 19
Message-ID: <slrnt4kni1.ohv.spamtrap42@one.localnet>
Reply-To: spamtrap42@jacob21819.net
X-Trace: individual.net v9FbPriMM33bYrO2MdX3twrXjDVLIeM/cLV0wgNTC1ay6UY8jG
Cancel-Lock: sha1:GoOep9RbOVV5okBErxUmGkNe6NI=
User-Agent: slrn/1.0.3 (Linux)

by: Robert Riches - Mon, 4 Apr 2022 02:56 UTC

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
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)

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

<dwE*p3QKy@news.chiark.greenend.org.uk>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=4514&group=comp.sys.raspberry-pi#4514

copy link Newsgroups: comp.sys.raspberry-pi

Path: i2pn2.org!i2pn.org!aioe.org!nntp.terraraq.uk!nntp-feed.chiark.greenend.org.uk!ewrotcd!.POSTED!not-for-mail
From: theom+news@chiark.greenend.org.uk (Theo)
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'
Date: 04 Apr 2022 10:15:43 +0100 (BST)
Organization: University of Cambridge, England
Lines: 17
Message-ID: <dwE*p3QKy@news.chiark.greenend.org.uk>
References: <slrnt4kni1.ohv.spamtrap42@one.localnet>
NNTP-Posting-Host: chiark.greenend.org.uk
X-Trace: chiark.greenend.org.uk 1649063745 7321 212.13.197.229 (4 Apr 2022 09:15:45 GMT)
X-Complaints-To: abuse@chiark.greenend.org.uk
NNTP-Posting-Date: Mon, 4 Apr 2022 09:15:45 +0000 (UTC)
User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (Linux/3.16.0-11-amd64 (x86_64))
Originator: theom@chiark.greenend.org.uk ([212.13.197.229])

by: Theo - Mon, 4 Apr 2022 09:15 UTC

Robert Riches <spamtrap42@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
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

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

<jb0aedFjnmrU1@mid.individual.net>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=4515&group=comp.sys.raspberry-pi#4515

copy link Newsgroups: comp.sys.raspberry-pi

Path: i2pn2.org!i2pn.org!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: email@here.invalid (Adrian Caspersz)
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'
Date: Mon, 4 Apr 2022 14:34:04 +0100
Organization: Keep Usenet Text Newsgroups Alive!!
Lines: 15
Message-ID: <jb0aedFjnmrU1@mid.individual.net>
References: <slrnt4kni1.ohv.spamtrap42@one.localnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net TsRvPF/mvU/WuF+9Q1BHgAe3oQ/aaWHg3ZqeZwQEIXeAEn4DC4
Cancel-Lock: sha1:a808yMMLF5CeBk0mLx1MsNkPpko=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.7.0
Content-Language: en-GB
In-Reply-To: <slrnt4kni1.ohv.spamtrap42@one.localnet>

by: Adrian Caspersz - Mon, 4 Apr 2022 13:34 UTC

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.

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

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

<awE*4bSKy@news.chiark.greenend.org.uk>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=4516&group=comp.sys.raspberry-pi#4516

copy link Newsgroups: comp.sys.raspberry-pi

Path: i2pn2.org!i2pn.org!aioe.org!nntp.terraraq.uk!nntp-feed.chiark.greenend.org.uk!ewrotcd!.POSTED!not-for-mail
From: theom+news@chiark.greenend.org.uk (Theo)
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'
Date: 04 Apr 2022 15:34:08 +0100 (BST)
Organization: University of Cambridge, England
Lines: 24
Message-ID: <awE*4bSKy@news.chiark.greenend.org.uk>
References: <slrnt4kni1.ohv.spamtrap42@one.localnet> <jb0aedFjnmrU1@mid.individual.net>
NNTP-Posting-Host: chiark.greenend.org.uk
X-Trace: chiark.greenend.org.uk 1649082851 18224 212.13.197.229 (4 Apr 2022 14:34:11 GMT)
X-Complaints-To: abuse@chiark.greenend.org.uk
NNTP-Posting-Date: Mon, 4 Apr 2022 14:34:11 +0000 (UTC)
User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (Linux/3.16.0-11-amd64 (x86_64))
Originator: theom@chiark.greenend.org.uk ([212.13.197.229])

by: Theo - Mon, 4 Apr 2022 14:34 UTC

Adrian Caspersz <email@here.invalid> wrote:
> 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.
>
> Have a look at the bottom of here.
>
> https://support.zoom.us/hc/en-us/articles/360037195152-Sending-a-problem-report-and-client-logs

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:
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

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

<slrnt4ndl5.14a.spamtrap42@one.localnet>

copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=4517&group=comp.sys.raspberry-pi#4517

copy link Newsgroups: comp.sys.raspberry-pi

Path: i2pn2.org!i2pn.org!aioe.org!news.mixmin.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: spamtrap42@jacob21819.net (Robert Riches)
Newsgroups: comp.sys.raspberry-pi
Subject: Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'
Date: 5 Apr 2022 03:25:25 GMT
Organization: none-at-all
Lines: 32
Message-ID: <slrnt4ndl5.14a.spamtrap42@one.localnet>
References: <slrnt4kni1.ohv.spamtrap42@one.localnet>
<jb0aedFjnmrU1@mid.individual.net> <awE*4bSKy@news.chiark.greenend.org.uk>
Reply-To: spamtrap42@jacob21819.net
X-Trace: individual.net k5JALn563AO5a7GNdf0ASwgU261bcT9uH4nmsWO2IDP902MCH+
Cancel-Lock: sha1:v8GIE147g+6zkCNWMo3P81jRxa4=
User-Agent: slrn/1.0.3 (Linux)

by: Robert Riches - Tue, 5 Apr 2022 03:25 UTC

On 2022-04-04, Theo <theom+news@chiark.greenend.org.uk> wrote:
> Adrian Caspersz <email@here.invalid> wrote:
>> 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.
>>
>> Have a look at the bottom of here.
>>
>> https://support.zoom.us/hc/en-us/articles/360037195152-Sending-a-problem-report-and-client-logs
>
> 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:
> 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

Thanks for that pointer about enabling Chromium logs!

--
Robert Riches
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)

Subject	Author
Raspbian 10/buster, Chromium, 'Aw, snap!...'	Robert Riches
Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'	Theo
Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'	Adrian Caspersz
Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'	Theo
Re: Raspbian 10/buster, Chromium, 'Aw, snap!...'	Robert Riches