Scratch Disk issue, Photoshop is filling all space in my harddrive via System Dat a

[Simon301454337j9z]

I've been encountering a persistent Scratch Disk issue in Photoshop despite following the recommended troubleshooting steps. My Mac is running on macOS Sonoma, and even with over 300GB of free space on my hard drive, the Scratch Disk error persists. Upon checking my storage usage while Photoshop is open, I noticed that System Data is consuming an unusually large amount of space, reaching up to 300GB. I couldn't find any effective method to clear this System Data, so I opted for a complete reinstall of my Mac.

After the fresh installation, everything is running on the latest versions, including Photoshop. However, the Scratch Disk issue remains. When Photoshop is closed, I have around 900GB of free space and System Data occupies only 18GB. But as soon as I open Photoshop, the free space plummets to almost zero, and System Data balloons to 860GB again (screenshots attached).

I'm at a loss as to what's causing this sudden surge in System Data usage and how to rectify the Scratch Disk problem. Any assistance would be greatly appreciated.

[Shangara Singh]

Sounds like a Photoshop bug when running in Sonoma. Been avoiding updating to it since it came out, so cannot help.

That said, scratch disk data and recovery data is usually cleared when you close Photoshop, so no need to reinstall OS (yeah!). There are utilities for cleaning up data. I thought there was one in macOS but cannot find it.

I partitioned my main drive so data is kept separate from "stuff" and use the "stuff" partition as a first scratch disk, and macOS HD as third, though that wouldn't help you.

SSDs are very cheap, consider adding one. I added one to store all my photo files, and use it as a second scratch disk. It's mounted at start up, so always accessible. 

[D Fosse]

It sounds like you're trying to open an enormous file by mistake. Anything bigger than, say, 15 000 pixels long side is probably a mistake.

[Trevor.Dennis]

That thing when, 'I could have sworn image size was in pixels, but it turned out to be inches and at 300ppi the document somehow managed to be a zillion pixels square'.

[Shangara Singh]

Oh, 30,0000x30,0000px files. Well...Upside is I discovered 15GB of recovered files while searching for larg files.

I'd forgotten how to do it in Finder, so found the files while poking in Storage and clicking on the (i) icons.

Why Apple hide options when searching until you instigate a search is a mystery, and another forum. 

[Ged_Traynor · Accepted solution]

@D Fosse looks like you hit the nail on the head

[Trevor.Dennis]

Hah!  Well spotted Ged.  That is far and away the most outrageous canvas size I have ever seen attempted on this forum.  It reminds me of when Patrick McGowan caused The General (some sort of super computer) to self destruct in The Prisoner.

This excerpt from Wikipedia describes what happened.

Number Six is interrogated but refuses to reveal the complicity of Number Twelve. Number Two claims that the "General" will know who his accomplice was. The "General" is revealed to be a sophisticated, experimental mainframe computer which has purportedly been programmed to be able to answer any question put to it. As Number Two is about to ask who assisted Number Six, Number Six states that there is a question that the "General" cannot answer. Number Two arrogantly accepts the challenge; when Number Six feeds his brief question into the "General", the computer begins to sputter and emit smoke after its data banks fail to find the answer to the question.

Fearing the worst, the Professor tries to shut down the computer, and as it begins to overload, Number Twelve tries to rescue the professor. The "General" self-destructs, killing both men in the process. A distraught Number Two asks Number Six what the question was. The General, and Number Two's plans, were destroyed by a simple epistemological trick: "Why?"

If the OP suffered nothing worse than a clogged Scratch drive, I'd say he was lucky!  😉

[Shangara Singh]

The General, and Number Two's plans, were destroyed by a simple epistemological trick: "Why?"

Ha, ha! ChatGPT and community forums beware! One way to make community forums self-destruct is by asking a question and not supplying basic document or system info. Then, as more and more people wade in and try to find a solution, forum is overwhelmed, resources consumed, computer core overheats, self destructs, taking Adobe and San Jose with it. Had OP not posted a screenshot or the Properties panel was closed in the screenshot, who can say there'd still be a forum today?

[bohdan_0045]

Bro you saved me, thanks from the deep of my heart, I registered here only to thank you