It's been months now and this issue is still causing so many problems.
Within minutes of opening Lr Classic and doing anything (grid, Develop, etc), all available VRAM will be consumed and most computers will become unusable if any other apps are opened which need to use the GPU.
People are increasingly complaining about Lr and system performance and this is the primary issue which is contributing.
Here's a SS showing what happens within a few seconds after you open Lr and develop a single image using only the basic sliders.
Does no one at Adobe care about this bug?
The same issue here. GPU VRAM disappears and then all other apps that need to use it just slow to a crawl. I use Lightroom CC 10.2 and after a few mintues of editing photos it has sucked up all VRAM and won't let it go even if I close all the photos I've been editing on. Then anything that really uses the GPU slows to a crawl. The only way is to close LR which is a major, major frustration.
Over a year later and still an issue, surely it can't be that hard to remedy?
If you haven't already done so, then update to 10.3, which should improve VRAM useage and release
I had a similar experience where I'd use 18/24 GB of VRAM on my card, and other programs like Photoshop would give warning about insufficient VRAM. DxO's raw demosaic tool, which heavily uses GPU features to process images, would go from processing them in a few seconds, to taking up to a minute when VRAM usage is high, likely because of swapping data in and out.
I'm running on a 7700k with a RTX 3090, with 32gb of system ram, and NVME/SSD disk.
I was looking at the 3090 myself, hoping it would not be AS susceptible to the leak. I mean you would think it would be better with it’s 32gb of ram. However, I from your post it sounds like it still gets just as bogged down as the rest of the GPUs. Am I correct?
The issue is not RAM it's having large quantities VRAM (i.e. more than 4GB) available for the Camera Raw component to swallow up and hold on to. LrC 10.3 should have improve GPU VRAM management compared to earlier versions, and work is ongoing to further improve VRAM management.
Unfortunately, my issue and most everyone elses issue is two fold. 1) It eats 100% of the GPU ram as soon as you do anything in the develope tab and only lets it go after you have shut down the program. and 2) the library tab slowly eats your CPU ram so you have to restart the program after sorting 2000-3000 photos or so.
The GPU leak is quick and there is only a couple of Gb of ram so it's more noticible. The CPU ram leak is slower and there is far more Gbs to eat before it becomes a problem, so it's not as noticible. But it's still there. I have a program that monitors both CPU and GPU ram and I have sent the proof to Adobe and they have confirmed my results. Hell, a couple times there were sharing a screen with me as it ticked up. Yet I still don't see a fix for either issue. (and I've been complaining for several years about it while using 2 different PCs in that time).