Environment: Antigravity IDE 1.107.0 (Electron 39.2.3), Arch Linux (Omarchy) kernel 7.2.5, standalone Linux install under ~/.local/opt/antigravity-ide.
What happened: A background utility process crashed with SIGSEGV during normal use (the editor stayed open – this is a Node.js utility subprocess, not the main window). The command line shows it is the node.mojom.NodeService utility process. The main IDE window and other processes kept running; no visible data loss.
Root cause, from a symbolized core dump: The crash is inside the bundled @parcel/watcher v2.5.1 native module (resources/app/node_modules/@parcel/watcher/build/Release/watcher.node), which ships unstripped. The crashing frame, symbol-resolved via gdb:
std::_Sp_counted_deleter<DirTree*, DirTreeDeleter, std::allocator<void>, __gnu_cxx::_Lock_policy::_S_atomic>::_M_dispose()
mov (%r10),%r8 ; load a DirTree pointer from the shared_ptr control block
test %r8,%r8
je <skip> ; null check passes
mov (%r8),%r12 ; SIGSEGV here
At the time of the fault, register r8 held the value 0xbadbad00badbad00 – a non-null but invalid pointer, consistent with a freed/poisoned DirTree pointer. This looks like a use-after-free: a shared_ptr control block was disposed with a DirTree pointer that had already been freed elsewhere, likely a race during directory-tree teardown/rebuild in the watcher’s Linux/inotify backend.
The app binary and watcher.node are both dated 2026-08-13 (unchanged for weeks), so this is not tied to a recent update – it’s a latent bug in the bundled watcher version that got triggered by some filesystem event.
Repro: No isolated repro yet – happened during normal editing/file-watching activity on a workspace.
Ask: Since this crashes inside the vendored parcel-bundler/watcher release 2.5.1, it may be worth checking whether a newer release fixes a known DirTree use-after-free, or filing upstream if not already tracked.