Your message dated Wed, 8 Jul 2026 16:06:22 -0400
with message-id <[email protected]>
and subject line Re: chromium: SIGTRAP crash at startup with --no-first-run;
breaks all chromedriver sessions
has caused the Debian Bug report #1141618,
regarding chromium: SIGTRAP crash at startup with --no-first-run; breaks all
chromedriver sessions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1141618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1141618
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 150.0.7871.46-1~deb12u1
Severity: important
X-Debbugs-Cc: [email protected]
Since 150.0.7871.46-1~deb12u1, chromium crashes with SIGTRAP within
about one second of startup when --no-first-run is on the command
line. Nothing is logged before the trap (it looks like a release-build
CHECK/NOTREACHED). Because chromedriver adds --no-first-run to every
launch by default, every chromedriver/selenium session fails with
"session not created: Chrome instance exited. Examine ChromeDriver
verbose log to determine the cause."
Reproduced on arm64 and amd64, in Docker containers based on
bookworm-slim (tested in node:24-bookworm-slim), with Xvfb as the display
server.
Reproduce (no chromedriver needed):
apt-get update && apt-get install -y chromium xvfb
Xvfb :99 -screen 0 1280x720x24 &
DISPLAY=:99 chromium --no-sandbox --disable-gpu \
--disable-dev-shm-usage --kiosk --enable-logging \
--remote-debugging-port=0 --user-data-dir=/tmp/ud \
--no-first-run "data:,"
Result: the process dies with "Trace/breakpoint trap". Removing
--no-first-run makes it start normally and write DevToolsActivePort.
A/B verification on identical stock containers, same Xvfb setup and
identical command line, only the chromium version differing:
149.0.7827.196-1~deb12u1 (from snapshot.debian.org): starts, prints
"DevTools listening on ws://127.0.0.1:...", keeps running
150.0.7871.46-1~deb12u1: Trace/breakpoint trap
Additional detail from debugging: the trap is at a fixed location,
ELF vaddr 0xaf711d8 in the arm64 binary (a "bti j; brk #0" landing
pad). The adjacent crash-annotation string in the binary is
"TemplateURLRef::HandleReplacement" (components/search_engines). The
crash also reproduces through a plain chromedriver InitSession even
when --no-first-run is removed via excludeSwitches, so there appear
to be additional triggers on the same code path; --no-first-run is
the simplest deterministic one.
Impact: any automation (selenium/chromedriver, CI, kiosk recorders)
using Debian's chromium is broken on bookworm since this version. We
are pinning 149.0.7827.196-1~deb12u1 from snapshot.debian.org as a
workaround.
--- End Message ---
--- Begin Message ---
Hi,
This should be fixed with 150.0.7871.100-1~deb13u1. Please reopen if
it's not.
Thanks,
Andres
On Tue, 7 Jul 2026 14:04:38 +0200 =?UTF-8?B?TsOhbmRvciBCw61yw7M=?=
<[email protected]> wrote:
Package: chromium
Version: 150.0.7871.46-1~deb12u1
Severity: important
X-Debbugs-Cc: [email protected]
Since 150.0.7871.46-1~deb12u1, chromium crashes with SIGTRAP within
about one second of startup when --no-first-run is on the command
line. Nothing is logged before the trap (it looks like a release-build
CHECK/NOTREACHED). Because chromedriver adds --no-first-run to every
launch by default, every chromedriver/selenium session fails with
"session not created: Chrome instance exited. Examine ChromeDriver
verbose log to determine the cause."
Reproduced on arm64 and amd64, in Docker containers based on
bookworm-slim (tested in node:24-bookworm-slim), with Xvfb as the display
server.
Reproduce (no chromedriver needed):
apt-get update && apt-get install -y chromium xvfb
Xvfb :99 -screen 0 1280x720x24 &
DISPLAY=:99 chromium --no-sandbox --disable-gpu \
--disable-dev-shm-usage --kiosk --enable-logging \
--remote-debugging-port=0 --user-data-dir=/tmp/ud \
--no-first-run "data:,"
Result: the process dies with "Trace/breakpoint trap". Removing
--no-first-run makes it start normally and write DevToolsActivePort.
A/B verification on identical stock containers, same Xvfb setup and
identical command line, only the chromium version differing:
149.0.7827.196-1~deb12u1 (from snapshot.debian.org): starts, prints
"DevTools listening on ws://127.0.0.1:...", keeps running
150.0.7871.46-1~deb12u1: Trace/breakpoint trap
Additional detail from debugging: the trap is at a fixed location,
ELF vaddr 0xaf711d8 in the arm64 binary (a "bti j; brk #0" landing
pad). The adjacent crash-annotation string in the binary is
"TemplateURLRef::HandleReplacement" (components/search_engines). The
crash also reproduces through a plain chromedriver InitSession even
when --no-first-run is removed via excludeSwitches, so there appear
to be additional triggers on the same code path; --no-first-run is
the simplest deterministic one.
Impact: any automation (selenium/chromedriver, CI, kiosk recorders)
using Debian's chromium is broken on bookworm since this version. We
are pinning 149.0.7827.196-1~deb12u1 from snapshot.debian.org as a
workaround.
--- End Message ---
