Yesterday I’ve installed Photolab 9.11.0. The update delivers 2 new cameras and a few minor bug fixes, but it introduced a major bug. The program runs out of memory after editing a few images (Nikon Z8 .nef) especially when local adjustments come are used.
My Mac M3 Pro with 16GB raises an out of memory error due to PL 9.11 uses 55,38GB of virtual memory. After aborting PL and restarting, I’m able to continue editing a handful of images before the same error comes up again. Editing becomes a pain in the A…
I find PL terribly slow on my M4 iMac with 16 gig when masking is employed. I just think the software has out grown my Mac and I do not expect any improvement when the next release comes out - in fact I expect it to worsen as they bring on more advanced functionality. It is odd though as Lr is fine.
Unfortunately, memory continues to be an issue. And I suspect high memory requirements will continue as the norm. Not just for PL. My M4 iMac has 32 MB, and I have never encountered “out-of-memory” problems. Of course, I haven’t yet downloaded 9.11. I will return here to report if I experience any issues after I try 9.11.
In recognition of this trend, my next computer purchase will be a Mac Mini (M5, 6, … ?) maxed out with 48 Mb. Trying to stay ahead of the curve and future proof my computer needs. I believe we will continue needing more and more powerful computers to keep up with software advances.
I realize none of this actually helps the OP. But I think more memory is the only currently viable solution. And like I said, not just as it relates to PL. I also think that DxO is overly optimistic with their listed “minimum requirements”.
I have a an issue which I believe is related. I’m using a M1 Max Mac Studio with 64GB of RAM, running MacOS Tahoe 26.6.2, DXO PhotoLab 9.11.0. I am having performance problems in the past week with the monitor redrawing repeatedly during display of the preview loupe, sometimes just failing to display the preview. Looking at memory usage with Activity Monitor, I find that the system is using swap (virtual memory) whilst running PL, despite there being large amounts of unused RAM available. During my last editing session, 10 swap files were created. I wonder whether this is either related to problematic changes in MacOS memory management in Tahoe 26.6, or a bug in PL 9.11 (or a combination of both things). Either way it is extremely irritating to be having these problems when I have a machine with 64GB of RAM…
Hi Uwe. I’m using a MAC pro M1, Photolab update is the same you are speaking about (9.11.0 build 54) and the camera is also the same (Nikon Z8). I do not use the compressed .nef files because the preview in MAC does not work with this file type (maybe they fix it in the mean time), but the sis not the point. The files are the largest dimensions the camera creates for a picture. I’ve not troubles at all even uploading 600-700 pictures in Photolab for the editing. What I’ve noticed is that Photolab is getting slower in rendering the images and exporting them, but is still working very well.
I know, this comment does not help you. I do hope provides you a useful information to solve the issue.
No problem with me using a 42mp Sony A99ii and editing hundreds of RAW photos. Windows 11 desktop, 16GB system memory and NVidia 3060 video card with 12GB of Video memory. When I check resources PhotoLab uses very little system memory and about 8GB of Video Ram. There have been people reporting problems with video cards with 8GB of VRam.
A is an update for my problems with PL 9.11 and memory usage:
The growth of the memory footprint of PL 9.11 shows up, when using local adjustments.
I’ve a series of 73 images of birds in flight and these need local adjustments of light and contrast. When I edit theses files the virtual memory of PL grows steadily. My Mac Pro M3 has 16Gb of physical memory and 64Gb of virtual memory. PL sucks up to 55 GB and the OS stops giving memory to PL. Today this occured after editing 40 pictures. But the problems start earlier. When virtual memory is twice as large as physical memory, the system starts heavy swapping and gets slower and slower and response time becomes to large for a decent workflow.
I have sent a bug report to DxO support including some images and .dop files and a log of the session. I hope, this helps with finding the memory leak.
So be aware, that if you use heavy local adjustment on 45G pixel images and you don’t have 64GB or even more of physical memory, you can get into performance issues and memory problems.
Not MacOS, but Win11. 40x Nikon Z8 raw processed (Exported) fine.
All photos with basic global adjustments + 3 x AI Pre-defined mask (Subject, Background, Peoples - all mask has multiple adjustment), NR: DP3. Parallel export: 3
System memory usage of PL + Export process approx 15GB (i have 32GB)
GPU memory usage is around 9GB+, but as i see, under Windows the Export use up all free GPU memory. Masks AI model itself may around 4GB+
My Mac Studio M2 with 32GB is working flawless. My 2020 MBP M1 with only 16GB which I use when I travel, works just as well. Will see how future updates will affect the Macs, but for now I am very pleased.
)