Participating Frequently

Lumetri Scopes causes "out of system memory"

Forum|Forum|3 years ago
May 26, 2023
7 replies
849 views

If I leave Lumetri Scope open (typically with RGB Parade and Waveform on 'float') over night then I will return to a "You have run out of system memory" OS arror. Premiere will have consumed 300+GB of memory. Premiere will show as "Paused". There is a 'resume' button, but it does not work even long enough to save or quit Premiere. The only solution is to force quit Premiere.

Steps attempted to resolve:

-- Remember to close the Lumetri panel - WORKS

-- Trash preferences (including dissabling the Creative Cloud sync) and cache - ERROR

-- Restart Mac / Reset Mac Pram etc - ERROR

-- Disable non-Adope plugins - ERROR

Steps to confirm:

-- Restart everything / Creat new, empty Premiere project / Add one h264 video file, open Scopes / Leave overnight - ERROR

-- Same as above but with ProRes 444 - ERROR

MacPro 2019

OS : 12.5 Monterey

CPU: 3.2 GHz 16-Core Intel Xeon W

RAM: 192 GB 2933 MHz DDR4

GPU: 2x AMD Radeon Pro W5700X 16 GB

Performance or Stability

Amy the Stuv

Community Manager

Hello everyone,

I’m working through some of these older reports and apologize for the lack of response. Thanks for sharing these detailed steps and observations. We understand how disruptive this behavior can be.

When possible, please update to the latest version of Premiere Pro and try the same test again with Lumetri Scopes open. Recent releases include ongoing improvements to memory management and overall stability, so your results would help confirm whether the behavior persists in the current version.

As a precaution, we recommend saving your work, closing the Scopes panel, and quitting Premiere Pro before leaving the system unattended. If the issue continues, please share the Premiere Pro version/build, OS version, Chip / GPU specs, and whether the same behavior occurs in a new, empty project.

Thank you,

Amy

R Neil Haugen

Legend

That would be so annoying, btw ... I use scopes heavily. The Mark I Eyeball is a mostly decent relative tool, but completely lousy at any absolute checking of anything.

Hope this gets sorted for you.

Everyone's mileage always varies ...

T

Tina37166069551w

Participating Frequently

I am aware. I've already been through all the details with Adobe and they have been unable to reproduce. I just wanted to let OP know he is not alone since this topic had no replies for a year since it was originally posted.

R Neil Haugen

Legend

Thanks for the details. Those things matter.

Everyone's mileage always varies ...

T

Tina37166069551w

Participating Frequently

M2 Ultra Mac Pro, 192 GB RAM, Ventura. Happens with any kind of media, MXF, MOV, mp4, etc. No issues until the scopes get pulled up. If the scopes panel is never opened during a session, there are never any problems. But as soon as the scopes panel comes up and you continue working, the memory leak begins and it fills up all available memory quickly. Like I mentioned, Premiere 2023 and earlier did not do this on the same machine. So to me, it is something within the Premiere 2024 scopes panel.

R Neil Haugen

Legend

Details on your systems would be handy. OS, hardware, and maybe even media.

I'm running a 3960x Ryzen, 128GB of RAM, 2080Ti. But I can't replicate either. I have no memory issues with the scopes ... and as color is my main thing, I nearly always have the scopes up hours at at time. So details again would be helpful to figure out exactly where/when this happens.

Everyone's mileage always varies ...

T

Tina37166069551w

Participating Frequently

Yes, there is absolutely a massive memory leak in Premiere when the lumetri scopes are up. This first started happening to me in Premiere 2024 and continues on 24.3 (2023 on the same computer is totally fine...no issues with scopes and memory leaks). This is a huge hamper to my workflow since I always like to have my scopes up. I have talked directly with Adobe about this and provided project files and they say they have not been able to reproduce the issue on their end. I really hope they figure this out soon but in the meantime the only workaround is to simply not use the scopes. Or if you do, you need to monitor your memory and then close out the panel when you're done and restart the app.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.