Skip to main content
Participant
Nov 21, 2026 3:04 PM UTC
Open for Voting

Premiere Pro 27.0 jumps to 120+GB of memory use on a simple project, then crashes every time.

Premiere Pro 27.0 is crashing every time I use it. MacOS tells me it's using too much memory — usually 120 GB — and pauses it, won't resume it and I need to force quit. I have an M1 Max MacBook Pro with 32GB RAM and 270GB free HD space. I'm editing a simple project: one video and one audio track, about 12 Sony XAVC files from my a6700, using only the Warp Stabilizer effect. Computer runs out of memory every time I use the new Color Mode. I tried clearing the media cache and decreasing Premiere's RAM allotment to 23GB, and I have no other applications open, but it still crashes. When I edit the same files in the old version 26.5 it works fine, only crashes in the new version.

    2 replies

    Participant
    Nov 21, 2026 3:57 PM UTC

    If the same clips edit fine in 26.5 and only 27.0 climbs to 120 GB of memory, this is a 27.0 problem, not your Mac or the XAVC files. Warp Stabilizer is already memory hungry, and the new Color Mode looks like the switch that sets it off. For work you need to finish now, stay on 26.5. In 27.0, turn the new Color Mode off and see whether memory stays reasonable. If you still want stabilizer in 27, transcode the camera files to a ProRes or DNxHR proxy and stabilize that, rather than running stabilizer plus the new color pipeline on the original clips. Clearing the cache and lowering the memory slider will not cap a process already allocating 120 GB. Send Adobe the memory or crash report, because a 32 GB machine should not need four times that much RAM on a simple timeline.

    Translate
    Participant
    Nov 21, 2026 5:11 PM UTC

    Thanks. I upgraded to MacOS 27.2.1 in case that made a difference and reset all Premiere settings. Just tried editing the same project again and this time it just crashed with no warning after about 10 minutes of working in Color Mode. Even before the crash Color Mode was not very responsive before the crash — there’s a noticeable lag between adjusting the exposure and seeing the result on screen. Seems like a better tool for color but I can’t use it until Adobe finds a way to make it more stable and efficient on what was a nearly top-of-the-line Mac 5 years ago. I’m going to stay in 26.5 for now.

    Translate