WebProcess CRASHED error is seen on executing webkit related testcases

Affected images versions

• not relevant (explain why)
• see the table below (list the build id and the apt or ostree deployment of the tested images in the appropriate cells)

Type	Arch	v2021	v2022	v2023pre
minimal/fixedfunction	amd64
minimal/fixedfunction	armhf
minimal/fixedfunction	arm64
target/hmi	amd64		x	x
target/hmi	armhf		x	x
target/hmi	arm64
basesdk	amd64		x	x
sdk	amd64		x	x
nfs	amd64
nfs	armhf
nfs	arm64
lxc	amd64
lxc	armhf
lxc	arm64
image-builder
package-source-builder

To find the build id and the variant type you can:

• derive it from the image name
  • for instance, with the apertis_ostree_v2022pre-fixedfunction-amd64-uefi_20211031.0425.img.gz image the build id is 20211031.0425, the variant is fixedfunction the deployment type is ostree
• obtain it from /etc/os-release using the BUILD_ID and VARIANT_ID keys

Unaffected images versions

• apertis v2022 20220831.0116 collabora

Testcase

https://qa.apertis.org/testcases/v2024dev2/webkit2gtk-ac-3d-rendering.html https://qa.apertis.org/testcases/v2024dev2/webkit2gtk-gstreamer1.0.html https://qa.apertis.org/testcases/v2024dev2/webkit2gtk-mt-touch-events.html

Steps to reproduce

Execute the above testcases on the SDK / target

Expected result

tests should pass

Actual result

user@apertis:~$ /usr/lib/*/webkit2gtk-4.0/MiniBrowser webkit2gtk/video.html

(MiniBrowser:2630): dbind-WARNING **: 10:54:03.943: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files
Could not determine the accessibility bus address
libEGL warning: DRI2: failed to authenticate

** (MiniBrowser:2630): WARNING **: 10:54:04.622: WebProcess CRASHED
libEGL warning: DRI2: failed to authenticate

** (MiniBrowser:2630): WARNING **: 10:54:10.266: WebProcess CRASHED

Reproducibility

How often the issue is hit when repeating the test and changing nothing (same device, same image, etc.)?

Put the ✅ in the most appropriate entry:

1. always

Impact of bug

low

Attachments

Add further information about the environment in the form of attachments here. Attach plain text files from log output (from journalctl, systemctl, …) or long backtraces as attached files. If adding comments on the log is required create a new snippet and add the link to it here.

Screenshots and videos are usually useful for graphic issues.

Root cause

tbd

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T9437