Sporadic SIGSEGV: native addon .got.plt reset to unrelocated file offsets

### Version v25.8.2 ### Platform ```text Linux sultan-box 6.18.6 x86_64 GNU/Linux V8: 14.1.146.11-node.24 ``` ### Subsystem vm, deps (V8 memory management) ### What steps will reproduce the bug? The crash occurs sporadically when a native addon (`better-sqlite3` v12.8.0) is loaded and the process is performing stdio pipe I/O. I have not been able to produce a minimal standalone reproducer; the crash happens approximately once per day under sustained use of a Node.js MCP (Model Context Protocol) plugin that communicates via stdin/stdout pipes and uses `better-sqlite3` for local FTS5 search. Command line: ``` node /home/sultan/.claude/plugins/cache/context-mode/context-mode/1.0.53/start.mjs ``` ### How often does it reproduce? Is there a required condition? Approximately 1-2 times per day under active use. 9 crashes observed over 7 days (March 24-30, 2026). All crashes occur during libuv stream read callbacks on the main thread. ### What is the expected behavior? Why is that the expected behavior? The process should not crash. Native addon PLT/GOT resolution should remain intact for the lifetime of the process. ### What do you see instead? SIGSEGV (signal 11) in the main thread. The systemd journal shows the crash at near-null addresses (`0x12566` or `0x120b6`) with unsymbolized JIT frames, but **GDB analysis of the coredump reveals the real cause: the entire `.got.plt` section of `better_sqlite3.node` has been reset to its on-disk (unrelocated) state.** ## Detailed Analysis ### Crash path (from GDB) ``` #0 0x0000000000012566 in ?? () #1 Database::JS_prepare() from better_sqlite3.node [+86: return addr after call to v8::Value::IsObject@plt] #2 0x00007fcd82d8fb4d in ?? () [V8 JIT trampoline] ... #17 v8::Function::Call() #18 node::InternalCallbackScope::Close() #19 node::InternalMakeCallback() #20 node::AsyncWrap::MakeCallback() #21 node::StreamBase::CallJSOnreadMethod() #22 node::EmitToJSStreamListener::OnStreamRead() #23 node::LibuvStrea…