Architectural Invariant Design: KMP Metal/Vulkan GPU Swapchain Lifecycle Eviction & Surface Drain Standard
KMP Metal/Vulkan GPU Swapchain Lifecycle Eviction & Surface Drain Standard defines an industrial-grade behavioral standard for mobile engineering. Enforces deterministic tearing down and recreation of Skia/Metal and Vulkan rendering surfaces during mobile app backgrounding transitions. Eliminates OS-level Jetsam termination (iOS 0x8badf00d/memory pressure kill) and Android VK_ERROR_SURFACE_LOST_KHR crashes by synchronously draining inflight GPU command buffers and purging GPU-backed swapchains. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.
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 active CAMetalLayer/VkSwapchainKHR buffers across lifecycle background transitions | 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. |
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 register platform lifecycle hooks (UIApplication.didEnterBackgroundNotification / Android Lifecycle.Event.ON_STOP) to trigger synchronous GPU pipeline drains.
Engineers MUST ALWAYS register platform lifecycle hooks (UIApplication.didEnterBackgroundNotification / Android Lifecycle.Event.ON_STOP) to trigger synchronous GPU pipeline drains.
Engineers MUST synchronously wait for inflight command buffers via MTLCommandBuffer.waitUntilCompleted() or vkQueueWaitIdle() before releasing native swapchain surfaces.
Engineers MUST synchronously wait for inflight command buffers via MTLCommandBuffer.waitUntilCompleted() or vkQueueWaitIdle() before releasing native swapchain surfaces.
Code MUST explicitly evict the Skia DirectContext resource cache using DirectContext.freeGpuResources() or DirectContext.purgeUnlockedResources(true) upon backgrounding.
Code MUST explicitly evict the Skia DirectContext resource cache using DirectContext.freeGpuResources() or DirectContext.purgeUnlockedResources(true) upon backgrounding.
Engineers MUST NOT attempt to schedule new draw passes, present CAMetalDrawable, or invoke vkQueuePresentKHR after background transition callbacks initiate.
Engineers MUST NOT attempt to schedule new draw passes, present CAMetalDrawable, or invoke vkQueuePresentKHR after background transition callbacks initiate.
Services MUST isolate swapchain recreation behind a lazily evaluated surface state machine that reconstructs GPU targets strictly after application resume signals.
Services MUST isolate swapchain recreation behind a lazily evaluated surface state machine that reconstructs GPU targets strictly after application resume signals.
Components NEVER hold strong references to CAMetalLayer, ANativeWindow, or SkSurface instances within persistent singleton scopes.
Components NEVER hold strong references to CAMetalLayer, ANativeWindow, or SkSurface instances within persistent singleton scopes.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is KMP Metal/Vulkan GPU Swapchain Lifecycle Eviction & Surface Drain Standard critical for AI coding assistants?
Enforces deterministic tearing down and recreation of Skia/Metal and Vulkan rendering surfaces during mobile app backgrounding transitions. Eliminates OS-level Jetsam termination (iOS 0x8badf00d/memory pressure kill) and Android VK_ERROR_SURFACE_LOST_KHR crashes by synchronously draining inflight GPU command buffers and purging GPU-backed swapchains. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.
Q:How does adopting this rule prevent AI hallucinations?
This rule explicitly declares what the AI must avoid (Retaining active CAMetalLayer/VkSwapchainKHR buffers across lifecycle background transitions) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.
Q:Which AI coding environments are supported?
This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).
Q:Can I combine this rule with other technology stacks?
Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.