Photoshop: Generating massive temp files on localdisk when localdisk is NOT set as scratch

  • 1
  • Problem
  • Updated 4 months ago
  • (Edited)
Lately Photoshop has been generating massive temp files on my local disk (C) which fill the drive and freeze the system. My scratch disks have never been set to C -- I have a separate M2 drive exclusively for PS Scratch -- and yet it now generates 20+GB scratch files on the C drive no matter what the scratch settings are. I have also checked all scratch disk settings in Bridge and associated apps, confirming none are set to C. Does anyone know why this is happening?

Seems like the only way to really make sure is reinstall the entirety of CC to the Scratch disk....but thought someone else may have advice.
Photo of Richard Thompson III

Richard Thompson III

  • 8 Posts
  • 3 Reply Likes

Posted 4 months ago

  • 1
Photo of eartho

eartho

  • 844 Posts
  • 219 Reply Likes
are you using lots of embedded smart objects?
Photo of Richard Thompson III

Richard Thompson III

  • 8 Posts
  • 3 Reply Likes
Not tons. The files in question are well layered PSBs assembled from 100MP raw files. So very large dimensions by photo standards, true 16bit, and sometimes 15 photo layers per file. A compressed/saved file will be about 3-6GB, and uncompressed / working in PS the memory profile is about 8-12GB.

The system has 128GB of RAM, 12GB video memory, and multiple M2 nand disks for flash/scratch/storage. The size of the files has not been a problem in the past. Just wondering why it's suddenly playing favorites with the localdisk.
(Edited)
Photo of eartho

eartho

  • 806 Posts
  • 197 Reply Likes
if you have any layers which are embedded SO's then Ps caches those to the C drive rather than the scratch. It's a ridiculous bit of ancient coding which should have been changed ages ago, but has remained and caused major issues for many of us in the industry.
Photo of Richard Thompson III

Richard Thompson III

  • 8 Posts
  • 3 Reply Likes
Wow, that's unfortunate :-( I guess I'll have to either totally reinstall CC or change my SO workflow to accommodate this "bit of ancient coding". Reinstall seems more likely. How could this have been omitted for so long? Seems like a really simple problem to fix :-(
Photo of eartho

eartho

  • 806 Posts
  • 197 Reply Likes
you can use linked smart objects (instead of embedded) to get around this issue.