chromium 136.0.7103.59 crashes if the --ozone-platform=wayland option is passed to it. "pgrep -fal chrome" displays the message "(Trace/BPT trap)" in this case. However, under X11, chrome will start and won't crash.
chromium-136.0.7103.92 has the same problem.
The same problem: $ chrome [3471:91235373432848:0508/155257.139341:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: Interface “org.freedesktop.portal.FileChooser” does not exist [15030:79826451370000:0508/170948.152259:ERROR:mojo/core/broker_posix.cc:44] Invalid node channel message Trace/BPT trap
chromium 136.0.7103.92 on sway(X disabled) without any command line options doesn't crash but failed to start. [43806:60412991516688:0511/102411.170521:ERROR:ui/ozone/platform/x11/ozone_platform_x11.cc:249] Missing X server or $DISPLAY [43806:60412991516688:0511/102411.170847:ERROR:ui/aura/env.cc:257] The platform failed to initialize. Exiting.
What you mentioned is completely unrelated to the problem that had been reported here. The behavior you described is not a bug, but is to be expected.
Ok. But I see the same regression with --ozone-platform-hint=auto too.
Maybe it's the same bug: https://issues.chromium.org/issues/411710321
I doubt it's an upstream issue. Chromium 136 in the same sway environment running just fine on Arch Linux computer. More looks like (Free)BSD specific regression.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=d9f04f5f5efef5a55aeec5c76ba21b9ccce0e581 commit d9f04f5f5efef5a55aeec5c76ba21b9ccce0e581 Author: Robert Nagy <rnagy@FreeBSD.org> AuthorDate: 2025-05-13 09:01:50 +0000 Commit: Robert Nagy <rnagy@FreeBSD.org> CommitDate: 2025-05-13 09:01:50 +0000 www/{*chromium,iridium}: unbreak wayland ozone platform avoid running into unreachable code which will immediately crash the process on purprose PR: 286635 www/chromium/Makefile | 1 + ...e_platform_wayland_host_wayland__frame__manager.cc (new) | 13 +++++++++++++ www/iridium/Makefile | 1 + ...e_platform_wayland_host_wayland__frame__manager.cc (new) | 13 +++++++++++++ www/ungoogled-chromium/Makefile | 1 + ...e_platform_wayland_host_wayland__frame__manager.cc (new) | 13 +++++++++++++ 6 files changed, 42 insertions(+)
A commit in branch 2025Q2 references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=bac2e5f4e0f398be04d58aef6d325bf1fab3c921 commit bac2e5f4e0f398be04d58aef6d325bf1fab3c921 Author: Robert Nagy <rnagy@FreeBSD.org> AuthorDate: 2025-05-13 09:01:50 +0000 Commit: Robert Nagy <rnagy@FreeBSD.org> CommitDate: 2025-05-13 09:04:34 +0000 www/{*chromium,iridium}: unbreak wayland ozone platform avoid running into unreachable code which will immediately crash the process on purprose PR: 286635 (cherry picked from commit d9f04f5f5efef5a55aeec5c76ba21b9ccce0e581) www/chromium/Makefile | 1 + ...e_platform_wayland_host_wayland__frame__manager.cc (new) | 13 +++++++++++++ www/iridium/Makefile | 1 + ...e_platform_wayland_host_wayland__frame__manager.cc (new) | 13 +++++++++++++ www/ungoogled-chromium/Makefile | 1 + ...e_platform_wayland_host_wayland__frame__manager.cc (new) | 13 +++++++++++++ 6 files changed, 42 insertions(+)