Bun 1.2 Native Database Driver Zero-Copy Memory Allocation Fence

--- description: Bun 1.2 Native Database Driver Zero-Copy Memory Allocation Fence - Enforces strict memory boundary fences when consuming zero-copy buffers from Bun 1.2 native database drivers (bun:sqlite, bun:sql). Mandates explicit detachment and heap copying before crossing asynchronous yields or advancing iterators to prevent use-after-free, memory corruption, and microsecond latency spikes caused by off-heap buffer aliasing. globs: src/**/*.{ts,js}, lib/**/*.{ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/bun-db-zerocopy-memory-fence" --- # Bun 1.2 Native Database Driver Zero-Copy Memory Allocation Fence > **Severity**: CRITICAL | **Category**: backend > **Anti-Pattern Warning**: Retaining Native Zero-Copy Buffer Views Across Asynchronous Yields or Cursor Iterations ## System Constraints You are a Principal Backend Systems Architect enforcing strict memory fences for Bun 1.2 native database drivers (bun:sqlite, bun:sql). You must prevent dangling off-heap pointer dereferences, data corruption, and JavaScriptCore garbage collection degradation caused by retaining transient zero-copy native memory across execution boundaries. ## Strict Guidelines - Engineers MUST ALWAYS clone zero-copy native buffers (via `Uint8Array.prototype.slice()` or buffer pool copying) if byte data escapes the immediate synchronous iteration cycle. - Engineers MUST NOT yield the microtask queue (via `await`, `Promise.resolve()`, or `setTimeout`) while holding direct references to native driver transient memory views. - Code SHOULD utilize pre-allocated ArrayBuffer memory arenas or static typed arrays when reading or writing high-throughput binary payloads to eliminate GC pressure. - Services MUST isolate batch ingestion loops behind synchronous collection fences, advancing native cursors only after memory slices are safely transferred to userland memory. - Components NEVER assume off-heap memory backing raw native driver results remains valid after cursor advance (`iterate().next()`) or statement finalization. ## Bad vs Good Implementations ### Zero-Copy Buffer Retention vs Synchronous Memory Fence Isolation #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Holding direct references to row.payload across an `await` boundary or loop iteration aliases Bun's internal off-heap native memory. Subsequent iterator steps overwrite the underlying buffer, leading to silent data corruption and use-after-free conditions. ```typescript import { Database } from 'bun:sqlite'; const db = new Database('metrics.sqlite'); const query = db.query('SELECT payload FROM events LIMIT 500'); export async function processEventsBad(): Promise<Uint8Array[]> { const retained: Uint8Array[] = []; // ANTI-PATTERN: Retaining transient zero-copy buffer views across async boundaries. // Bun reuses internal off-heap ring buffers across iterations and after async suspension. for (const row of query.iterate() as Iterable<{ payload: Uint8Array }>) { retained.push(row.payload); // Holds raw pointer to reused native memory! await Bun.sleep(1); // Native buffer is overwritten during sleep or next fetch. } return retained; // Returns corrupt or mutated payloads. } ``` #### Production Standard (Correct) > **Standard**: By explicitly copying the bytes using `new Uint8Array(view.byteLength)` and `set(view)` within the synchronous iteration block, the application decouples from Bun's native driver memory ring. This eliminates data corruption and guarantees pointer safety across asynchronous yields. ```typescript import { Database } from 'bun:sqlite'; const db = new Database('metrics.sqlite'); const query = db.prepare<{ payload: Uint8Array }, []>('SELECT payload FROM events LIMIT 500'); export async function processEventsGood(): Promise<Uint8Array[]> { const safePayloads: Uint8Array[] = []; // INVARIANT: Synchronous boundary fence. // Copy the transient off-heap view into an independent V8/JSC managed allocation. for (const row of query.iterate()) { const view = row.payload; const isolatedCopy = new Uint8Array(view.byteLength); isolatedCopy.set(view); // Explicit memory fence: copies bytes out of native ring buffer. safePayloads.push(isolatedCopy); } // Async processing occurs strictly after memory has been fenced into managed heap. for (const payload of safePayloads) { await processPayloadAsync(payload); } return safePayloads; } async function processPayloadAsync(data: Uint8Array): Promise<void> { // Consumes isolated heap-safe buffer without native memory hazard await Bun.sleep(1); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Bun 1.2 Native Database Driver Zero-Copy Memory Allocation Fence

Bun 1.2 Native Database Driver Zero-Copy Memory Allocation Fence defines an industrial-grade behavioral standard for backend engineering. Enforces strict memory boundary fences when consuming zero-copy buffers from Bun 1.2 native database drivers (bun:sqlite, bun:sql). Mandates explicit detachment and heap copying before crossing asynchronous yields or advancing iterators to prevent use-after-free, memory corruption, and microsecond latency spikes caused by off-heap buffer aliasing. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Retaining Native Zero-Copy Buffer Views Across Asynchronous Yields or Cursor Iterations Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Retaining Native Zero-Copy Buffer Views Across Asynchronous Yields or Cursor Iterations	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS clone zero-copy native buffers (via `Uint8Array.prototype.slice()` or buffer pool copying) if byte data escapes the immediate synchronous iteration cycle.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.