1. Forum
  2. FidoNet
  3. RBERRYPI

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

    From Robert Riches@3:770/3 to All on Mon Apr 4 02:56:01 2022
    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.)

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Robert Riches on Mon Apr 4 10:15:43 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Adrian Caspersz@3:770/3 to Robert Riches on Mon Apr 4 14:34:04 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Theo@3:770/3 to Adrian Caspersz on Mon Apr 4 15:34:08 2022
    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

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From Robert Riches@3:770/3 to Theo on Tue Apr 5 03:25:25 2022
    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.)

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)