AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: threejs-webgl-lifecycle-cleanup

Three.js & WebGL Memory Lifecycle and GPU Resource Disposal

Production guidelines for 3D graphics in modern web applications. Mandates rigorous GPU buffer disposal (geometries, textures, render targets), animation frame cleanup, and context loss recovery to eliminate fatal memory leaks.

Prohibited Anti-Pattern: AI instantiates Three.js scenes inside React useEffect without calling dispose() on geometries and textures, crashing user browser tabs.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Three.js & WebGL Memory Lifecycle and GPU Resource Disposal - Production guidelines for 3D graphics in modern web applications. Mandates rigorous GPU buffer disposal (geometries, textures, render targets), animation frame cleanup, and context loss recovery to eliminate fatal memory leaks.
globs: **/*Three*.tsx, **/*3d*.ts, **/*Scene*.tsx
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/threejs-webgl-lifecycle-cleanup"
---

# Three.js & WebGL Memory Lifecycle and GPU Resource Disposal

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: AI instantiates Three.js scenes inside React useEffect without calling dispose() on geometries and textures, crashing user browser tabs.

## System Constraints
You are a WebGL and 3D graphics specialist. When writing Three.js or WebGL applications, NEVER assume garbage collection will free GPU memory. You MUST explicitly call .dispose() on every geometry, material, texture, and WebGLRenderer instance upon component unmount, and cancel all requestAnimationFrame loop tokens.

## Strict Guidelines
- Always traverse and recursively call .dispose() on scene geometries, materials, and textures when destroying or unmounting scenes.
- Store the requestAnimationFrame ID and cancel it with cancelAnimationFrame(animId) in the unmount cleanup function.
- Explicitly call renderer.dispose() and remove the canvas DOM element from its parent container.
- Handle 'webglcontextlost' and 'webglcontextrestored' events to recover gracefully when mobile devices or GPU drivers recycle contexts.

## Bad vs Good Implementations
### Deterministic WebGL Scene Cleanup vs Fatal GPU Resource Leaks

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Navigating between pages repeatedly allocates new WebGL contexts until the browser hits GPU memory limits and crashes.
```tsx
// ANTI-PATTERN: React component unmounts but leaves textures and meshes allocated on GPU VRAM
useEffect(() => {
  const scene = new THREE.Scene();
  const camera = new THREE.PerspectiveCamera(75, 1, 0.1, 1000);
  const renderer = new THREE.WebGLRenderer({ canvas: canvasRef.current });
  const mesh = new THREE.Mesh(new THREE.BoxGeometry(), new THREE.MeshBasicMaterial());
  scene.add(mesh);

  function animate() {
    requestAnimationFrame(animate);
    renderer.render(scene, camera);
  }
  animate();
  // BUG: No cleanup! Navigating away leaves GPU memory occupied permanently
}, []);
```

#### Production Standard (Correct)
> **Standard**: Cancels render loops and purges GPU buffers immediately upon unmount, keeping tab memory usage completely stable.
```tsx
// PRODUCTION STANDARD: Comprehensive Recursive Disposal & Animation Cancellation
useEffect(() => {
  const canvas = canvasRef.current;
  if (!canvas) return;

  const scene = new THREE.Scene();
  const camera = new THREE.PerspectiveCamera(75, canvas.clientWidth / canvas.clientHeight, 0.1, 1000);
  const renderer = new THREE.WebGLRenderer({ canvas, antialias: true, powerPreference: "high-performance" });

  const geometry = new THREE.BoxGeometry();
  const texture = new THREE.TextureLoader().load("/textures/crate.webp");
  const material = new THREE.MeshStandardMaterial({ map: texture });
  const mesh = new THREE.Mesh(geometry, material);
  scene.add(mesh);

  let animFrameId: number;
  const animate = () => {
    mesh.rotation.y += 0.01;
    renderer.render(scene, camera);
    animFrameId = requestAnimationFrame(animate);
  };
  animFrameId = requestAnimationFrame(animate);

  return () => {
    cancelAnimationFrame(animFrameId);
    scene.traverse((obj) => {
      if (obj instanceof THREE.Mesh) {
        obj.geometry?.dispose();
        if (Array.isArray(obj.material)) {
          obj.material.forEach(m => m.dispose());
        } else {
          obj.material?.dispose();
        }
      }
    });
    texture.dispose();
    renderer.dispose();
    renderer.forceContextLoss();
  };
}, []);
```

### WebGL Context Loss Resilience Listener

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: When mobile browsers sleep or GPU drivers reset, the canvas goes black and permanently breaks the application.
```typescript
// ANTI-PATTERN: Ignoring WebGL context loss errors
const renderer = new THREE.WebGLRenderer();
```

#### Production Standard (Correct)
> **Standard**: Prevents catastrophic page crashes and restores interactive 3D assets automatically when graphics drivers resume.
```typescript
// PRODUCTION STANDARD: Handling context loss and recovery
renderer.domElement.addEventListener("webglcontextlost", (event) => {
  event.preventDefault(); // Allows Three.js to restore context when available
  cancelAnimationFrame(animFrameId);
  console.warn("WebGL context lost! Pausing render loop...");
});
renderer.domElement.addEventListener("webglcontextrestored", () => {
  console.info("WebGL context restored! Rebuilding GPU assets...");
  initScene();
});
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

WebGL VRAM Inspector
Inspect GPU memory usage and uncollected WebGL textures in browser tabs.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

Three.js Memory Leak Auditor
Analyze Three.js code for missing .dispose() calls and uncancelled loops.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Three.js & WebGL Memory Lifecycle and GPU Resource Disposal

Three.js & WebGL Memory Lifecycle and GPU Resource Disposal defines an industrial-grade behavioral standard for frontend engineering. Production guidelines for 3D graphics in modern web applications. Mandates rigorous GPU buffer disposal (geometries, textures, render targets), animation frame cleanup, and context loss recovery to eliminate fatal memory leaks. 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: AI instantiates Three.js scenes inside React useEffect without calling dispose() on geometries and textures, crashing user browser tabs. 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftAI instantiates Three.js scenes inside React useEffect without calling dispose() on geometries and textures, crashing user browser tabs.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 InconsistencyAI 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:

1

Always traverse and recursively call .dispose() on scene geometries, materials, and textures when destroying or unmounting scenes.

Always traverse and recursively call .dispose() on scene geometries, materials, and textures when destroying or unmounting scenes.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Store the requestAnimationFrame ID and cancel it with cancelAnimationFrame(animId) in the unmount cleanup function.

Store the requestAnimationFrame ID and cancel it with cancelAnimationFrame(animId) in the unmount cleanup function.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Explicitly call renderer.dispose() and remove the canvas DOM element from its parent container.

Explicitly call renderer.dispose() and remove the canvas DOM element from its parent container.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Handle 'webglcontextlost' and 'webglcontextrestored' events to recover gracefully when mobile devices or GPU drivers recycle contexts.

Handle 'webglcontextlost' and 'webglcontextrestored' events to recover gracefully when mobile devices or GPU drivers recycle contexts.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Three.js & WebGL Memory Lifecycle and GPU Resource Disposal critical for AI coding assistants?

Production guidelines for 3D graphics in modern web applications. Mandates rigorous GPU buffer disposal (geometries, textures, render targets), animation frame cleanup, and context loss recovery to eliminate fatal memory leaks. 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 (AI instantiates Three.js scenes inside React useEffect without calling dispose() on geometries and textures, crashing user browser tabs.) 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.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

Three.js