Lightroom Classic 15.5: Anhaltender GPU-/WDDM-Ressourcenzustand verursacht massiven Performanceeinbruch in DxO PureRAW

Hi @Fam. NWSTMother. NWST,

Thank you for the exceptionally detailed report. I don’t want to ask you to repeat the troubleshooting you’ve already documented.

One thing that would help us narrow the trigger is whether the SLOW state can be reproduced after a long Lightroom session without using any AI/ML operations such as Denoise, Select Subject/Sky/People, or other masking features. Conversely, if the slowdown reliably follows one of those operations, please let us know which one.

Best,

Anshul Saini

Oh, I missed > most here is ENGLISH.
Waiting on reply AND most of ALL SOLUTION for this real and 99,999% Adbobe caused problem

On Windows 11, I've observed a reproducible GPU/WDDM-related issue with Lightroom Classic 15.5 that causes DxO PureRAW 6 to become extremely slow after prolonged GPU usage in Lightroom.

System: Windows 11 Build 26100, Lightroom Classic 15.5, Camera Raw 18.5, NVIDIA RTX 2070 SUPER 8 GB, Studio Driver 610.88, HAGS disabled. The issue is also reproducible with the GPU’s factory settings.

In a fresh Lightroom session, PureRAW runs normally: approximately 100–110 seconds for 15 RAF files, with GPU power consumption around 190–200 W, while PureRAW maintains a stable GPU working set of approximately 742 MiB.

Later in the same Lightroom session, PureRAW can become extremely slow with the same images and settings: 25–30 minutes for the same processing, sometimes with remaining time estimates of several hours. GPU utilization remains close to 100%, but power consumption drops to approximately 115–120 W. PureRAW then no longer maintains its normal GPU working set of about 742 MiB consistently, but typically fluctuates between approximately 70 and 230 MiB.

At the same time, there is heavy WDDM/VidMm residency and commitment activity. In a reproduced SLOW run, 458 VidMmProcessDemotedCommitmentChange events were measured for PureRAW, including repeated 512 MiB demotions, along with more than 143,000 commitment changes.

Key observations:

• Lightroom alone can trigger WDDM demotion events.
• Lightroom can maintain several GiB of WDDM LOCAL usage/commitment over an extended period.
• FAST and SLOW runs sometimes occur with similar total VRAM usage; therefore, the sheer amount of VRAM is not the cause.
• SLOW runs tend to occur when the Lightroom commitment approaches the WDDM budget.
• Restarting Lightroom reliably resolves the issue.
• Restarting PureRAW alone, toggling GPU acceleration ON/OFF, switching from Develop to Library, clearing the Camera Raw disk cache, or pressing Win+Ctrl+Shift+B do not reliably resolve the issue.
• Setting the NVIDIA CUDA System Fallback Policy to "Driver Default" does not prevent the error.
• The error is reproducible even without GPU overclocking.

The measurement data strongly suggests that Lightroom/Camera Raw can create a long-lasting GPU/WDDM residency and commitment state that later prevents PureRAW from maintaining its normal GPU workload in a stable, resident state.

Please check the following in particular:

• The duration and release of large GPU resources in Lightroom/Camera Raw
• WDDM LOCAL Commitment and behavior under budget pressure
• Residency/trim behavior after GPU-accelerated image processing
• Long-lived GPU contexts or queues
• Interaction with external GPU-accelerated plug-ins or applications within the same Lightroom session

Hello, ​@Fam. NWST  

My comments are not directed at you, they are directed at any forum MODERATOR that may read this message. The author of this post has spent a good deal of time formatting the text to be readable, with paragraphs and bullet items and so forth. But then when I click on translate and select English, all of that formatting is lost, and the result is one extremely long paragraph with no formatting at all, and so the result is essentially unreadable. This is unacceptable for the forum software to do this.