@tailwindcss/oxide segfaults when a process holds more than one Scanner (4.3.3, 4.3.5, linux-x64-gnu)#20707
What version of Tailwind CSS are you using?
@tailwindcss/oxide 4.3.5 (also 4.3.3), native @tailwindcss/oxide-linux-x64-gnu binding.
What build tool (or framework if it abstracts the build tool) are you using?
Seen first with @tailwindcss/vite 4.3.3 under Vitest 5. It reproduces with @tailwindcss/oxide alone in plain Node; see below.
What version of Node.js are you using?
v26.12.0. The crash also happens with other Node 26 builds.
What browser are you using?
N/A
What operating system are you using?
Arch Linux, x86_64, kernel 7.2, glibc
Reproduction URL
Self-contained script below, run against apps/web of https://github.com/pingdotgg/t3code (commit 7a64505a21e755498e6b85794124f3754265db38).
Describe your issue
When a process creates more than one Scanner and calls scan() on them, it intermittently dies with SIGSEGV, or sometimes SIGABRT. A single Scanner never crashed in 15 runs, even with repeated scan() calls. With 3 scanners × 3 rounds, about 1 run in 4 crashes.