Adobe Applications saying there isn't enough memory

Unfortunately, so far, from what I've read, you EITHER have Windows "automatically manage paging file size for all drives" or you do it... I can't find ANY way to to the "automatic manage" and tell it "but, not THAT drive"...

In my case, it DEFINITELY IS NOT picking the fastest drive - it MAY be the fasted spinning platter since there's only one, but it's a WHOLE lot slower than the SSDs everything else is on. IS there a way to tell "Automatically manage" but ONLY on these drives?

In any case, went into system and turned OFF "Automatically manage", set a system managed pagefile on C and on Z and removed the one on G. Rebooted. Checked to make sure things still were where I wanted them, rebooted again, just in case. C now has a 15GB pagefile (never got over 6 before) and Z has a 5GB one. Turned "Automatically manage" back on, which grays out everything so I couldn't see what happened to Z, but C still showed a pagefile and G did NOT.

Exited back out - it never squawked that I'd need to reboot - checked, and the pagefiles were still where I wanted them. REBOOTED again, and with "Automatically manage" turned on the system came up with the pagefile on G and NONE on C or Z. Do I need to go back to using the "System managed size" so I can specify the drive or is there a way to have Windows "Automatically manage" WITHOUT it splattering pagefiles wherever it THINKS they should go?

------
I just did a little rummaging asking how to specify drives when using "automatically manage" and found this:

By default, Windows configures virtual memory so that page files are automatically created on volumes as the Operating System determines is best. This Virtual Memory setting is called “Automatically manage paging file size for all drives”.


This makes me think I WON'T be able to use "Automatic manage" and will need to do something else like "System managed size" for pagefiles...

You should make a reasonable page file on your C:\ And create a large one on the drive "you" want. and not let windows manage this at all.

"I didn't read your reply correctly: To set DisablePagingExecutive to off it must be set to 1. The paging executive setting in Windows is used to load system files such as the kernel and hardware drivers to the page file when needed, disabling this will prevent windows from Paging Kernel and drivers and should keep your system snappier under heavy loads."

Just to make sure I've got this right... I just checked in the registry and DisablePagingExecutive is set to "1", so it IS disabled, right? Which is what I want? If I have this backwards, let me know...

As far as my technique and "HeavyLoad and BurnInTest"!
This ain't a technique, it's just slightly more than a normal day for photographers using Adobe products!

I've currently got the system set with a System managed pagefile on "C" and a System managed pagefile on "Z", so there's at least 150GB of SSD space available if it needs it for paging. The Scratch disk is also on an SSD and there's about 1.4TB of free space, so THAT shouldn't be a problem... Temp files and Photoshop temporary files go into a 50GB partition that's only used for temp files, so THAT should have plenty of space...

IN THEORY, other than letting Windows completely manage pagefiles, I should be about as good as I'm going to get, presuming I've done things right...

NEXT, and I put a topic in the forum for this, I have a 12GB chunk of unallocated space next to the O/S partition I'd like to extend "C" to use. My problem is the three hidden, unnamed little partitions right after "C" that I don't know how to deal with - but as I said, that's already in this forum, so hopefully somebody can tell me how to do that.

@GracieAllen,

That seems golden.

From your "test" description, your two main application are still competing for memory when you switch back an forth from one to another. this is the main problem that causes the exhaustion at some point.

When you're ready, I still suggest to upgrade to 64Gb ram to mitigate that phenomenon as much as possible.

Yeah, long term it sounds like anybody doing much of any real processing with these tools is going to need a LOT of memory. Something changed with one or both tools over the last couple years, 'cause I've always doing this kind of stuff and don't recall these kinds of problems...

The way these tools are going, along with the resource requirements of things like Topaz, next system I build is going to have to have a TON of memory and a LOT of horsepower... Every new release makes better use of multiple cores so it's going to be interesting...

It’s not FIXED, but it IS different…
Today I created a small HDR/PANO – 18 D850 shots, 6 sets of 3-each HDR images.

Sent the first 6 pano images from Lightroom to Photoshop. Set reposition and content-aware fill.
Panorama worked fine, CA fill FAILED with out of memory.
Cleared all cache, PS memory usage dropped about 1.5GB, fill still failed. Memory usage around 16GB at this point.
Flattened the image, fill still failed.
Cleared cache again, fill still failed.
It APPEARS that once this error appears, it NEVER goes away…

During processing I captured a little info. This is during processing the first 6 images.



Sent the SECOND set of 6 images, same settings.
Panorama worked, CA FILL failed with out of memory.



I missed the period where memory got to 31.9 but it did, and it sat there for several seconds before dropping back slightly.

Sent the THIRD set of 6 pano images, same settings. Same thing... It went between 31.4 and 31.9 GB of memory
Pano worked, CA fill failed.

I SAVED all three panoramas and told PS to do the HDR blend of the 3 panorama images.
It worked fine.




In the shot of the Task manager - I have no idea how to make it show you the image larger - you can see that the only things using a significant amount of energy are Adobe. With all the processing done, and the HDR output sitting there, Photoshop hung onto around 21.5 GB of memory. It also continued to show almost all the Scratch in use…
Went back to Lightroom, took the three panorama outputs and told Lightroom to do a Photo Merge HDR.



Lightroom sucked up a bunch of memory – I captured an image where PS was about 14.4GB and Lightroom was over 13.5 GB, but it’s missing at the moment…

Anyhow, eventually Lightroom failed on the HDR – again, it’s never successfully created anything NEAR this size, and memory dropped back to “normal”…

BUT, it seems like once Photoshop displays that “out of memory” popup, it never goes away no matter how much memory I give it back. Clearing cache doesn’t help, deleting all the images and reloading them doesn’t help. Only thing that works is shutting down Photoshop and restarting it…

My OTHER question is why does Photoshop show 23.4GB for scratch space when the scratch drive has more than 1.2 TB of free space. There were about 25GB of photoshop temp files on the scratch disk, but there’s a HUGE amount of free space if needed. What would have happened if the 23.4 PS thinks is there had gotten exhausted?

And BTW, even when it showed 31.9 in use of 31.9 GB, Efficiency NEVER dropped below 100%.

And LAST BUT NOT LEAST, a shot of the screen showing HALF the memory on the system is available and Photoshop STILL won't do the content-aware fill...

Hi Gracie,

Sorry to ear you are still plagued with that problem.

It's normal for the program to remain in an inconsistent state after the memory ran out, I think Photoshop does not calculate the memory required for the "external " function to succeed, resulting it the error. The memory used by Photoshop for documents is not released but rather flagged as free in the program, for a much faster reuses when needed. Once your machine reaches a certain point in used RAM. Launching another process that can only be done in ram is causing the process to overrun.

If you are open to try a different approach.

Limit the memory used by Photoshop to half.
I don't know about Lightroom settings, if memory control is available do the same there.

And also a thing a couple heavy Photoshop users told me... Is to disable hyper-threading on Intel CPUs...
Since you have a 12 threads CPU, I thought I could mention it, running on 6 cores is enough for your application.
It would stop the CPU hardware to share a single set of execution resources for two "virtual cores". It's easy to test. And it has been reported giving a small increase in performance under Photoshop benchmarks. I hope it could also help you in stability.

And again, you may end up Adding more RAM, because cutting back on the memory used by the program may give you more stability but, It might also ampere performance up to a point that you may not like it as much.

It's all to be tested, so you can decide if it reaches your expectations.

At the moment, it's much less of a problem than it was... Yes, it still doesn't want to do content-aware fill, but it DOES actually build panoramas and HDR, which would have killed it before.

So, it's acting BETTER. But again, even with half the memory on the system available, once Photoshop says it can't do something because of memory, it appears that it's NEVER going to do fill until Photoshop gets shut down and restarted...

I'll try cutting memory - at the moment it's at 96%, which was an earlier recommendation from one of the optimizing performance topics.

As far as I can tell, there's nothing in Lightroom to limit memory usage, or if there is, I haven't seen it.


---------------------------------
Update - just set memory for PS to 65%. First 6-image panorama dropped efficiency to 80%. So, I increased it to 70%. First panorama dropped it to 97%. Second and third stayed at 100%, but I'm watching Photoshop, which in theory is limited to about 18GB, blow right through 20GB and keep going......

I don't think it's the system anymore - that seems reasonably good. I think it's a Photoshop problem with the CA fill...

Some users are convinced there is a memory leak since 2018

That would fit - I DON'T recall having this problem in earlier versions, but don't know exactly when it started. I KNOW it was a problem as far back as PS 2020.