flutter_texture_rgba_renderer/macos/Classes
yunchan b87d45fd09 macos: drain an autorelease pool around each frame (Kitedesk T-4204)
FlutterRgbaRendererPluginOnRgba runs on the caller's thread, a Kitedesk
video thread, which has no autorelease pool and lives as long as the
session: an object autoreleased there would stay until the session ends
(pointed out in upstream PR #2). Each frame now runs in an @autoreleasepool.

On macOS 26.5.2 the frame path autoreleases nothing on that thread, before
and after this series (frames_leave_no_autoreleased_objects passes on
50efc18e too), so this is a guard: a probe saw CoreVideo autorelease objects
when a process first made an IOSurface on such a thread, and the engine's
registrar logs with NSLog for a frame announced to it after its engine is
gone, which the old code did on the video thread.

Tests: 13 of 13 pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-15 09:56:22 +09:00
..
TextRgba.swift macos: let closed textures' buffers go, keep closed identities (Kitedesk T-4204) 2026-11-15 09:56:22 +09:00
TextureRgbaApi.m macos: drain an autorelease pool around each frame (Kitedesk T-4204) 2026-11-15 09:56:22 +09:00
TextureRgbaRendererPlugin.swift macos: let closed textures' buffers go, keep closed identities (Kitedesk T-4204) 2026-11-15 09:56:22 +09:00