Mac Unreal Metal Memory Leak Report Gains Another Independent Reproduction

Long-running games can reveal problems that short editor tests overlook. A forum discussion about Unreal Engine's Metal rendering path on macOS received a meaningful new confirmation on October 31, 2026, when another developer reported reproducing an apparent drawable-retention leak in a packaged 5.8.4 build. This follows an initial October 28 report and an October 29 reproduction.

The original analysis points to a graphics-viewport function that appears to retain a drawable without balancing that operation with a release. In the affected scenario, the number of live Metal drawable objects reportedly increases as frames are presented. That can be particularly visible during long sessions or at high frame rates, where more objects accumulate over the same amount of time.

The October 31 contributor says the issue was independently reproduced on Apple Silicon with a different Metal shader path from the earlier test. The team rebuilt a patched engine from source and compared long-running gameplay sessions with and without the proposed renderer change. Their report includes heap-object counts and a second investigation involving autoreleased temporary objects in command submission. Those results are supplied by developers in the discussion; they are not an official vendor benchmark or an Epic-issued patch.

This distinction is important because fixes made against engine source code do not automatically affect a project using a precompiled launcher build. Even a promising source change requires a compatible rebuild, verification that the packaged executable contains the change, and regression testing of graphics output. Developers should avoid applying code snippets from a forum directly to a live release without review.

For a Mac-focused studio, the practical first step is measurement. Package a known test scene, let it run for a controlled duration, and watch process memory and relevant object allocations over time. Compare identical camera routes, frame-rate caps, and renderer settings where possible. Rising memory alone does not identify a leak; cache warm-up and other subsystems can also change memory consumption. Repeated snapshots and allocation evidence make a stronger case.

The report is relevant to developers shipping Unreal games for Mac, especially those seeing continuous memory growth over sustained play. It does not imply that the rendering problem affects Windows, Android, or every Metal configuration. An official fix should be confirmed in Epic release notes before being presented as resolved.