resource-management-audit

Memory leaks in OpenGL occur when textures, buffers, shaders, or framebuffers aren't properly deleted. Implement correct IDisposable patterns with _disposed flags, call GL.Delete methods explicitly, and use GC.SuppressFinalize to prevent finalizer execution that could crash the OpenGL context.

OpenGL calls in finalizers are unsafe because finalizers run on arbitrary threads without guaranteed context binding, causing crashes or undefined behavior. Always perform resource cleanup in Dispose methods, not finalizers, to ensure thread-safe context access.

Audit IDisposable implementation by verifying _disposed guard checks, confirming GL.Delete calls for each resource type, resetting resource IDs to zero, and calling GC.SuppressFinalize. Check factory-owned versus component-owned patterns to prevent premature disposal of shared resources.

Factory-owned resources are managed centrally and shared across components; components should not dispose them. Component-owned resources are created and managed by individual components with exclusive disposal responsibility. Mixing these patterns causes double-deletion or resource exhaustion.

GPU resource exhaustion manifests as memory leaks or crashes during repeated scene loads. Audit Mesh and Texture classes to ensure OpenGL IDs are correctly deleted on disposal, verify no orphaned resources accumulate, and confirm shared factory resources aren't disposed by individual components.

Yes, the audit checklist applies to all OpenGL resource types: textures, buffers, shaders, and framebuffers. The core pattern—IDisposable implementation, GL.Delete calls, ownership clarity, and disposal guards—remains consistent across resource types.