Bug#1006457: Chromium fails to start on aarch64 systems

[MichaIng]

Package: chromium
Version: 98.0.4758.102-1~deb11u1

Latest Chromium on Debian Bullseye fails to start on aarch64/arm64
systems. Different ones with different kernels were tested, though all
Linux 5.10 variants, using (and generally supporting) modesetting DDX.

Only v98 from security repo is affected, v90 from "regular" Bullseye
repo starts fine.

-------
[2380:2380:0220/184034.039483:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.122230:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.167681:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.198424:ERROR:system_web_app_manager.cc(320)]
Exceeded SWA install retry attempts. Skipping installation, will retry
on next OS update or when locale changes.
[2380:2380:0220/184034.200305:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.225990:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2380:2380:0220/184034.240862:ERROR:gpu_process_host.cc(978)] GPU
process exited unexpectedly: exit_code=6
[2380:2380:0220/184034.240968:FATAL:gpu_data_manager_impl_private.cc(448)]
GPU process isn't usable. Goodbye.
-------

The X server itself works well, any other X application starts fine, X
server logs show no errors, but a regular exit like when you exit the X
client. It's hence definitely Chromium itself which fails. We tried all
kind of GPU related flags, like "--disable-gpu", changing renderer,
disabling GPU rasterization and all such, any combination or skipping
all of them, even the ones shipped by default with the package
(/etc/chromium.d) makes no difference. Starting with xinit (as root),
startx or from desktop doesn't make a difference either.

Best regards,

Micha

[Andres Salomon]

On Fri, 25 Feb 2022 20:45:55 +0100 MichaIng wrote:
>
> Package: chromium
> Version: 98.0.4758.102-1~deb11u1
>
> Latest Chromium on Debian Bullseye fails to start on aarch64/arm64
> systems. Different ones with different kernels were tested, though all

> Linux 5.10 variants, using (and generally supporting) modesetting DDX.

Which boards did you test with?

What desktops were you using? Was this under X or wayland? Does it make a difference if you run chromium with --ozone-platform=x11 or --ozone-platform=wayland ?  What about --use-gl=desktop ?

[MichaIng]

Package: chromium
Version: 99.0.4844.74-1~deb11u1

> Which boards did you test with?

We observed the issue on these boards:
- Odroid C2
- Odroid C4
- Odroid N2+
- Radxa ROCK Pi 4
- Radxa Zero

> What desktops were you using? Was this under X or wayland? Does it
make a difference if you run chromium with --ozone-platform=x11 or
--ozone-platform=wayland ? What about --use-gl=desktop ?

We face it on various X11 desktops and via xinit or startx from console.
Wayland was not tested.

--ozone-platform=x11 and/or --use-gl=desktop do not make a difference.

Best regards,

Micha

[Andres Salomon]

On Sat, 2 Apr 2022 00:06:04 +0200 MichaIng wrote:
>
> Package: chromium
> Version: 99.0.4844.74-1~deb11u1
>
> > Which boards did you test with?
>
> We observed the issue on these boards:
> - Odroid C2
> - Odroid C4
> - Odroid N2+
> - Radxa ROCK Pi 4
> - Radxa Zero
>
> > What desktops were you using? Was this under X or wayland? Does it
> make a difference if you run chromium with --ozone-platform=x11 or
> --ozone-platform=wayland ? What about --use-gl=desktop ?
>

Thanks. Do you have libglapi-mesa installed, and if so, what version? If not, does installing it help?

Same question for libgl1-mesa-dri.

[MichaIng]

I also just verified that both are installed, ah via chromium-common
indeed as dependencies.

> I have a rock64 board lying around unused, I'll have to hook it up to
a monitor and see what happens on there with xfce and chromium.

That would be great. While we tested it with installed desktop
environments as well, for plain X server + Chromium (for e.g. kiosk mode
usage), we install these packages explicitly:

--- X server ---
xserver-xorg-core
xserver-xorg-input-libinput
xinit
dbus-x11
xfonts-base
x11-xserver-utils
x11-utils
mesa-utils
mesa-utils-extra
--- Chromium ---
chromium
libpam-systemd

Best regards,

Micha

[Willem Mulder]

Hi,

On Sat, 2 Apr 2022 00:06:04 +0200 MichaIng <mi...@dietpi.com> wrote:
> We face it on various X11 desktops and via xinit or startx from console.
> Wayland was not tested.

We're seeing the same issue on the Raspberry Pi 4 with Wayland, running
Chromium through (self-packaged) cage:

Jun 13 17:10:55 kiosk-test cage[33117]:
[33117:33117:0613/171055.713668:ERROR:gpu_process_host.cc(973)] GPU
process exited unexpectedly: exit_code=6
Jun 13 17:10:55 kiosk-test cage[33181]: *** stack smashing detected ***:
terminated
Jun 13 17:10:55 kiosk-test cage[33182]: *** stack smashing detected ***:
terminated
Jun 13 17:10:56 kiosk-test cage[33117]:
[33117:33117:0613/171056.479403:ERROR:gpu_process_host.cc(973)] GPU
process exited unexpectedly: exit_code=6
Jun 13 17:10:56 kiosk-test cage[33185]: *** stack smashing detected ***:
terminated
Jun 13 17:10:56 kiosk-test cage[33186]: *** stack smashing detected ***:
terminated
Jun 13 17:10:56 kiosk-test cage[33117]:
[33117:33117:0613/171056.798637:ERROR:gpu_process_host.cc(973)] GPU
process exited unexpectedly: exit_code=6
Jun 13 17:10:56 kiosk-test cage[33187]: *** stack smashing detected ***:
terminated
Jun 13 17:10:56 kiosk-test cage[33188]: *** stack smashing detected ***:
terminated
Jun 13 17:10:57 kiosk-test cage[33117]:
[33117:33117:0613/171057.029048:ERROR:gpu_process_host.cc(973)] GPU
process exited unexpectedly: exit_code=6
Jun 13 17:10:57 kiosk-test cage[33189]: *** stack smashing detected ***:
terminated
Jun 13 17:10:57 kiosk-test cage[33190]: *** stack smashing detected ***:
terminated
Jun 13 17:10:57 kiosk-test cage[33191]: *** stack smashing detected ***:
terminated
Jun 13 17:10:57 kiosk-test cage[33117]:
[33117:33117:0613/171057.433252:ERROR:gpu_process_host.cc(973)] GPU
process exited unexpectedly: exit_code=6
Jun 13 17:10:57 kiosk-test cage[33192]: *** stack smashing detected ***:
terminated
Jun 13 17:10:57 kiosk-test cage[33193]: *** stack smashing detected ***:
terminated
Jun 13 17:10:57 kiosk-test cage[33117]:
[33117:33117:0613/171057.694622:ERROR:gpu_process_host.cc(973)] GPU
process exited unexpectedly: exit_code=6
Jun 13 17:10:57 kiosk-test cage[33117]:
[33117:33117:0613/171057.695223:FATAL:gpu_data_manager_impl_private.cc(450)]

GPU process isn't usable. Goodbye.

The security update that bumped chromium to version 102 hasn't changed
the situation.

Kind regards,

Willem Mulder

[Leonard Lausen]

This issue seems specific to the ~deb11u1 or ~deb11u2 packages. For example, both 97.0.4692.99-1~deb11u2 and 103.0.5060.134-1~deb11u1 crash but both 97.0.4692.99-1 and 103.0.5060.134-1 work. Could you please explain the difference between these builds?

(103.0.5060.134-1 does not work with --ozone-platform-hint=wayland which is a separate issue affecting aarch64 builds tracked in Bug#1016438)

[Andres Salomon]

The builds are almost identical, except for the compiler (clang 11) and
build environment used. Clang 13 has been backported to stable (it's
currently in stable-proposed-updates, and should be in the bullseye
11.5 release).

The next chromium upload should be built against clang-13, which may
behave better for you.

[MichaIng]

Great, also solved here, many thanks!

Best regards,

Micha