P: Gpu stops being used after opening many files

@DjAligator14 , we are not aware of any intentional change in this area; can you provide more details to make sure we are taking into account every step of your scenario?

Thanks

Again there is a problem with this. It worked fine but with the new version it started again. Not on low number but it still happening. Why you done it again it worked so good!!

Just had scrubby zoom stop working on an image whilke working through a large batch of images, only had 3 6"x4" 300ppi files open at the time it happened. Quiting photoshop and reopening file restored scrubby zoom operation.

Plus a complete program crash when rotating a layer, photoshop just dissapeared, no error report nor any recovered files when relaunched.

Adobe Photoshop Version: 24.7.0 20230612.m.2205 9cfa76c x64
Number of Launches: 16
Operating System: Windows 10 64-bit
Version: 10 10.0.19045.3086

@Mark.Dahm 

Here is what I'm experiencing - I would open and work through 30-50 images, with the GPU used for each document, without the problem. Then I would close all those and open another batch of 30-50. Some files at the end would the GPU issue where it's not used as the original issue of this thread, even if I close the files as I work through them. So for example I open 50 files, with 30 having the GPU used and 20 having the CPU used. I close the first 30, but the kast 20 still have the CPU used. When I quit photoshop and reopen all 50 images, then all 50 have the GPU used.
So it looks like to me it would still take an app restart to refresh the GPU resouces available.

Hey, just wanted to update you. I updated the regular version to the latest version, and gpu utilization is working correctly.  Strangly my alt tab issue is still not fixed( works correctly in beta, both the latest and version before, the one that had gpu utilization fix). If i make a small window and just drag and drop to photoshop it works like it should(i can move the file across the photoshop window, choosing to drop it as a new file on top bar, or a new layer in the current file), but if i have photoshop open in full screen and folder also in full screen, using alt+tab to switch the active window from folder to photoshop will trigger the release of the file by it self, effectively droping the file in photoshop where the mouse was hovering at the moment of alt tab release.  This is happening in the past few versions, but it is fixed in beta. I tried usual stuff, reinstalling, setting to default etc. I am not sure if you can follow what i am saying so i will give another example. Photoshop is running, folder with random images is also running on top of the photoshop both in full screen, i left click the image and drag it, then press alt+tab to switch to photoshop, my mouse button coordinates in pixels are lets say 700x700 pixels. As soon as i let go of alt tab, me golding the left click is ignored by photoshop and the file gets dropped at the same coordinated 700x700 pixels. I am not letting go of my left mouse button but it still happens, in the beta i can just keep moving(hovering) the file around on my svreen over photoshop until i let go of my left mouse button. I can also make a quick screen recording. Btw i am sorry because i am probably totally of the topic, but i find it hard to maneuver around the forums. Greetings

@Arseniy_S ,

Photoshop grabs RAM when it needs it, and releases it when you quit the app, but not while you're running.

While Photoshop is running, it will dynamically de-allocate document data when files are closed, and re-use it for newly opened documents. The net effect is that it may look like Photoshop is growing its RAM allocation, but it should actually only be taking what the largest document needs, then re-using that as documents open and close.

The total size of the RAM allocated could be large because the files are exceeding the size of the already allocated RAM. That is, anyway, how it's designed to work. We ran a few quick tests here using the Beta (which is essentially the same as the last version released, plus some other new stuff), and the RAM does release when Ps closes, and does not grow beyond the amount required by the document that requires the maximum amount of RAM. Let me know if you are seeing something different; thanks for noting this.

@Arseniy_S , that's bad behavior and we're looking into that; thanks for noting here.

@Mark.Dahm, one thing I wanted to bring up is that it seems like the memory usage accumulates with the increased number of images open, but it doesn't go down when I close them. So for example I've worked on 30-40 images, then closed them but my memory usage remained. Opening more images continued increasing the memory usage and was reducing the performance. Is this something that can be done with a change of setting or is the only way would be to restart the app?

Thanks @chrisfromneptune , would it be possible to share your script with us? I'm seeing a few reports of the white squares and this could help us track it down. Also, your system info output from Photoshop > Help would get us headed the right direction to solve the issue.

It mostly works well for me, but when running actionscript at the end of my workflow to flatten and save the open documents (about 30-35), one of the files ended up with a handful of large white squares, so had to reinstall the old version unfortunately.