Tauri 2.0 Multi-Window Shared Memory Frame Synchronization Standard

--- description: Tauri 2.0 Multi-Window Shared Memory Frame Synchronization Standard - Mandates atomic fence synchronization and triple-buffered shared memory structures for cross-window canvas streaming across decoupled Tauri 2.0 WebViews. Eliminates buffer tearing, out-of-order frame presentation, and garbage collection thrashing inherent in serializing frame buffers over the native IPC event bus. globs: src/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tauri2-multiwindow-shmem-frame-sync-standard" --- # Tauri 2.0 Multi-Window Shared Memory Frame Synchronization Standard > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Unsynchronized Raw Buffer Broadcasts via Tauri Event Bus Causing Frame Tearing and Serialization Bottlenecks ## System Constraints You are a Principal Software Architect enforcing zero-copy IPC and deterministic rendering invariants for Tauri 2.0 multi-window applications. Enforce atomic fence handshakes, triple-buffered shared memory consumption, and lock-free frame synchronization across isolated WebViews. Never permit serialization of high-frequency pixel buffers across the default Tauri IPC bridge. ## Strict Guidelines - Engineers MUST ALWAYS enforce triple buffering via lockless atomic index swaps when sharing framebuffers between decoupled Tauri 2.0 WebViews. - Engineers MUST NOT transfer multi-megabyte binary payloads, Base64 strings, or ArrayBuffers via Tauri's `emit` or `invoke` channels for high-frequency rendering (>= 30fps). - Consumers MUST synchronize buffer consumption with `requestAnimationFrame` and check monotonic sequence numbers to prevent processing stale or partially written frames. - Frontend rendering pipelines MUST release backbuffers through atomic signal channels immediately after GPU texture upload to eliminate backpressure stalls in writer windows. - Decoupled WebViews MUST initialize synchronization states using explicit lock-free SharedArrayBuffer atomics or low-overhead lightweight fence notification events carrying monotonic metadata only. ## Bad vs Good Implementations ### Cross-Window Frame Buffer Synchronization Protocol #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Sending full pixel arrays over Tauri's event serialization bridge saturates the IPC thread, incurs substantial JSON serialization overhead, triggers aggressive GC pauses, and produces visual tearing due to unsynchronized blitting while new frames arrive out of order. ```typescript import { emit, listen } from '@tauri-apps/api/event'; // ANTI-PATTERN: Serializing complete pixel buffers over Tauri IPC // Causes high GC pressure, IPC latency, race conditions, and visual tearing interface FramePayload { buffer: number[]; width: number; height: number; } export function setupTearingReceiver(canvas: HTMLCanvasElement) { const ctx = canvas.getContext('2d'); listen<FramePayload>('render-frame', (event) => { const { buffer, width, height } = event.payload; const clamped = new Uint8ClampedArray(buffer); const imgData = new ImageData(clamped, width, height); // Direct blit without synchronization or double-buffering guarantees tearing ctx?.putImageData(imgData, 0, 0); }); } ``` #### Production Standard (Correct) > **Standard**: Decouples data transfer from IPC payload serialization by passing atomic fence notices containing only sequence counters and slot indices. Frame blitting is locked to the refresh rate via `requestAnimationFrame` using triple-buffered slots, eliminating cross-window tearing and preventing IPC saturation. ```typescript import { invoke } from '@tauri-apps/api/core'; import { listen } from '@tauri-apps/api/event'; interface FrameFenceNotice { bufferSlotIndex: number; sequence: number; timestamp: number; width: number; height: number; } export class SynchronizedFrameConsumer { private canvas: HTMLCanvasElement; private ctx: ImageBitmapRenderingContext | null; private latestFence: FrameFenceNotice | null = null; private renderedSequence = -1; private isRunning = false; constructor(canvas: HTMLCanvasElement) { this.canvas = canvas; this.ctx = canvas.getContext('bitmaprenderer'); } public async initialize(): Promise<() => void> { this.isRunning = true; // Listen only for lightweight atomic fence notices (metadata only) const unlisten = await listen<FrameFenceNotice>('frame-fence-signaled', (event) => { if (event.payload.sequence > this.renderedSequence) { this.latestFence = event.payload; } }); requestAnimationFrame(this.renderLoop.bind(this)); return () => { this.isRunning = false; unlisten(); }; } private async renderLoop(): Promise<void> { if (!this.isRunning) return; const fence = this.latestFence; if (fence && fence.sequence > this.renderedSequence) { this.renderedSequence = fence.sequence; try { // Fetch zero-copy hardware buffer reference or transfer ImageBitmap via custom asset protocol const imageBitmap = await invoke<ImageBitmap>('acquire_shm_frame_bitmap', { slotIndex: fence.bufferSlotIndex, sequence: fence.sequence }); this.ctx?.transferFromImageBitmap(imageBitmap); // Release buffer back to the producer's triple-buffer pool await invoke('release_shm_buffer_fence', { slotIndex: fence.bufferSlotIndex }); } catch (err) { console.error('Frame synchronization drop:', err); } } requestAnimationFrame(this.renderLoop.bind(this)); } } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tauri 2.0 Multi-Window Shared Memory Frame Synchronization Standard

Tauri 2.0 Multi-Window Shared Memory Frame Synchronization Standard defines an industrial-grade behavioral standard for frontend engineering. Mandates atomic fence synchronization and triple-buffered shared memory structures for cross-window canvas streaming across decoupled Tauri 2.0 WebViews. Eliminates buffer tearing, out-of-order frame presentation, and garbage collection thrashing inherent in serializing frame buffers over the native IPC event bus. 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: Unsynchronized Raw Buffer Broadcasts via Tauri Event Bus Causing Frame Tearing and Serialization Bottlenecks 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	Unsynchronized Raw Buffer Broadcasts via Tauri Event Bus Causing Frame Tearing and Serialization Bottlenecks	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 enforce triple buffering via lockless atomic index swaps when sharing framebuffers between decoupled Tauri 2.0 WebViews.

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.