Photoshop Memory Leak

[PhotoTrip]

Good evening. I use both photoshop and lightroom CC for my image workflow on MacOS. I noticed recently that Lightroom was way behind and lagging when I moved through the grid, the images would take seconds to switch. This just started recently happening and I wanted to dig in. I nailed the problem down to Photoshop not releasing memory when I close images. I have many computers but take a Macbook Pro with a M2 MAX process, 32 GB of ram with me on the road. Typically I will edit for hours after a shoot. This involves a ton of graphics, especially when moving between lightroom and photoshop. Howevcer I don't usually have more that 5 images open at a time on PS. I close each image after editing to push bak into lightroom after adding graphic bat have found that Photoshop only releases partial memory for each image closed and memory grows progressively over time. Today I found that Photoshop was using over 22GB of ram at idle with no images open. 
I am currently on version 26.10.0. Sitting idle at startup PS uses @ GB. Strangely if I restart it fully loads the last amount of memory used on restart and then release all memory back down to 2GB. Normally I would attribute this to caching but something else is going on here because it doesn't reap the memory until I close and restart.

[Hyperlink to account with no posts removed by moderator. If the "@" symbol was a typo, let us know what you meant to type.]

[D Fosse]

This is normal and by design. 

Photoshop does not release memory when an image is closed. The memory is reused and recycled - but not released until you close the application.

This is what makes e.g. batch processing possible. Constantly requesting memory from the operating system would slow everything down.

Photoshop will use memory up to the limit you specify in preferences, so it's important to set the allocation at a level that leaves memory for other processes and applications. The default 70% usually works well.

[PhotoTrip]

That would be fine, however I set a 14GB limit on photoshop and it blew past it to 22GB on this machine.

Technically speaking batch mode is not the same as everyday workflow tasks. The use case would be resizing, watermarking and file concersions which I can do on the command line. Batch can't place logos and other graphics varaibly which requires lines of site and manual placement on compositions. Don't understand why Photoshop would use batch as it's first principle. I can close the app after each composition in my workflow but that comes at a cost to time.  Not my product so I can live within the constraints of the design for the tools I choose to use.

[D Fosse]

We see this (memory usage exceeding the allocation set in preferences) pop up from time to time. It's not common, but it happens. I've never seen it myself.

It's hard to pin down. Some users have reported that a full and complete reset of preferences fixed it. Others that a new version didn't have the problem. So on the face of it, it might look like a bug.

However, I'd like to take this opportunity to throw out a question to anyone reading this. On systems with an integrated GPU - which is where this mainly appears to be happening -  the GPU uses shared system memory, and it can eat up a lot performing Photoshop tasks. Many of the new advanced Photoshop functions run directly and entirely in the GPU. What I have never been able to establish, is where this GPU memory consumption gets listed. Under the application calling it? Under system? I'd be very grateful if somebody could point me to it.

[PhotoTrip]

I believe on the Mac it is listed under the application as part of the unified memory model. 

[PhotoTrip]

I will keep an eye on things on mys ide. I have a tendency to work on certain projects over days and don't always close the apps unless necessary. This workflow is different than my video work where I have a "media bin" that allows me to quickly accociate images and assets with a specific project across many workstreams. In photoshop however I have to organize externally and then Drag and Drop or open "recent". SOmethimes I work with so many files this eats away at time so I just keep the assets in memory until not needed. I understand how that can creep over time but just didn't expect ot to blow past the defined limits.

I will reset also and see if that changes the behavior.

[Raptorart]

yep, a few seconds of speed painting and it jumps up a couple 100 mb
normally it's 2k or under
but i watched it climb to 8.2k in memory
swapped back to ver 22 (before AI upgrade)
ver 25 and ver 26 both do it too with the mem leak