Skip to main content
Participating Frequently
November 7, 2019

P: Temp Files Filling Scratch Disk FAST (possible memory leak?)

  • November 7, 2019
  • 45 replies
  • 5220 views

I work with extremely large PSB files (~20-100 GB). Supercharged Windows 10 machine built for this purpose alone, that includes:

  • NIVIDIA Quadro P4000 (8 GB RAM)
  • 128 GB RAM
  • 1 TB OS Drive
  • 14 TB Data Drive
  • 4 TB Data Drive
  • 2 TB, RAID 0 scratch disk 

Previous project file was 50 GB and used approximately 500 GB of my scratch disk. Current project file is now reduced to 22 GB. After upgrade to PS 2020, I had to add 2 additional scratch disk options and TEMP files are now eating 4 TB and counting! It's creating anywhere from 3 to 8 new 64 GB Temp files every minute when using the program!

After spending 1 hour on tech support, I was told this is normal, expected behavior; to use 10+ times as much scratch disk space as Photoshop 2019!

Screen capture available here:
https://www.dropbox.com/s/r31dzyzsq1uiv2m/Photoshop-2020ScratchDiskIssue.JPG?dl=0

This topic has been closed for replies.

45 replies

jwen
Participant
November 20, 2019
Absolutely. I am happy enough to have a temporary solution for now that you have provided us with. Looking forward to the fix for this issue, cheers.
RosaPerry
Inspiring
November 20, 2019
Noel   That's an excellent explanation and clarification on things moving forward in Photoshop. Thanks so much.
Rosa
Participating Frequently
November 20, 2019
Thanks for letting us know the workaround was effective.  Please rest assured we're working a real fix for the issue.

As far as "if it ain't broken, don't fix it" goes in general...  I'm afraid we can't always comply; there's a real need for us to move our architecture forward.

As an analogy, you may choose keep your car for a long time, put on new tires, maintain parts that wear, even paint it...  Great!  It continues to do what it did.  But now and again you may crave a new model because new ones have an updated engine design under the hood to give you capabilities you did not have before.

In similar fashion, we need to update our underlying compositing engine design in order to be able to deliver new features and take advantage of modern computer hardware, not to mention run on new platforms.  You may not see the advantages of our new compositing engine in obvious ways just yet, but you will.

Thanks again and as always for your understanding and patience - and especially for your help identifying problems like this one - as we strive to improve one of the most complex pieces of software on the planet.  🙂

-Noel Carboni
 Adobe QE Developer
jwen
Participant
November 20, 2019
This worked for me, thank you. The Legacy Compositing suggestion worked. Saved my life when I was rushing for a deadline. But please, Photoshop team work on a solution for PS2020. Even if not a bug, there is no reason why this should be acceptable when every other Photoshop version has never caused an issue like this. If it ain't broken, don't fix it.
Inspiring
November 19, 2019
Hi again Noel,

Thanks for getting on this so quickly. Finally had the opportunity to try the workaround late last night and so far seems to allow general usability for PS 2020. Appreciate you getting on this problem right away and getting us all working again. Look forward to the final fix on a subsequent release.

Thanks again.
Participating Frequently
November 18, 2019
Hi Noel,

Thank you very much for your assistance! I remember using this Legacy Compositing for another issue in 2019 but did not test it for 2020. We'll give that a shot and report back.
Participating Frequently
November 18, 2019
I will add, we also work in non-destructive workflows as Phillip has described. And I agree, it might work for web-based art but not high-resolution for printing. Thank you Phillip for providing a file to Adobe for troubleshooting!
Participating Frequently
November 18, 2019
Update:

We have identified a workaround that has little downside and should allow you to use Photoshop 2020 for your big projects without blowing out your scratch space:

Go into Preferences > Performance and check the [ ] Legacy Compositing setting, then Quit and restart Photoshop.

Please let me know here if you continue to have any issues with scratch file sizes after doing the above.

Thanks!

-Noel Carboni
 Adobe QE Developer
Participating Frequently
November 18, 2019
Thank you everyone and especially Phillip and Greg.

We have received a file with which we can reproduce the issue where we are seeing more than 10x additional scratch data stored from Photoshop 2020 than with Photoshop CC 2019.  We're actively looking into it.

-Noel Carboni
 Adobe QE Developer
Inspiring
November 18, 2019
We are having the same issue on ~2GB files. Temp files of ~60GB are being created in Photoshop 2020 with every change. Mac 10.14.6. Just ridiculous and totally unworkable.