Hi, I went for the Present Sync option but after a short while I had a memory issue on my MacPro: PS was using a lot of it. After a while the machine was not responding at all. When I tried to disable the option a message said the sync was still in progress while trying to quit PS would say that I had to wait until the sync was completed. This lasted the night then the app crashed.
In other words it seems I'm unable to get out of it!
I repeated the process on my laptop with the same results, even deleting the settings.
Any similar issues/solutions? thanks!
Hi, I have the same issue since I activated yesterday the preset sync option. I tryed to disable - but I couldn't. My Macbook pro is only running hot. The only oprotunity to quit Photopshop is by Apple Finder option (force quit) . Also I get error message, libary sync error. I tryed sign-in sign out, quit cloud app, I deleted the settings - nothing changed.
How stopping it? Any ideas, thanks for help.
I had the Adobe support team working on my computer (one of the coputers) a full afternoon but they were unable to find a cause/solution. I'm still waiting.
What I did to keep working (since PS had boceme slow and unresponsive) has been going back to the previous version with Time Machine and it is working fine.
I I try to update again the problem is there again. I guess they have to find a solution.
Same issue for me on Windows. It seems there is a major memory leak. And it's indeed a loop :
- Preset syncing activated = PS always says it will close after preset syncing but the sync never ends and memory consumption increases until the computer crashes (force quit before it happens is preferable...).
- Trying to uncheck Preset Syncing in Preferences = Yes/No/Cancel prompt for keeping/not keeping Presets on Creative Cloud but all choices (except Cancel ofc) lead to the same memory issue, without actually removes the Preset Syncing option...
- Reset preferences does not remove Preset Syncing.
- Reinstalling PS does not remove Preset Syncing.
So what do we do now ? The only way to use this version of PS, when the issue occurs for the first time, is to force quit PS via Task Manager/Apple Finder every time we want to exit the app.
Please, Adobe, find us a fix or allow us to remove Preset Syncing without making Photoshop doing some dirty work in background that causes this explosion of RAM. My network isn't even used during this time (0.00MB/Sec) even though it's supposed to be a cloud sync.
So I uninstalled PS 22.2 and installed 22.1 and it seems to be working much better. At least it's usable and I can close it without having to force quit on my Macbook. Until they figure it out and send an update, seems the most reasonable solution.
I'm having the exact same issue since yesterday. I chose the preset sync option and now I can't close out of Photoshop without force quit and within Photoshop it's buggy too. The app has crashed several times and forced my new macbook pro to crash as well. Please help!
Ps. Like another user who posted on this issue, I also tried unsuccessfully to reset preferences but it does not remove Preset Syncing. I tried reinstalling PS but that doesn't remove Preset Syncing.
Hey there, I am facing the same issue since yesterday. Launching Photoshop 22.2 uses 99% RAM and after 2 minutes my whole system was crashing. I was not able to edit the checkbox to remove the checkmark for syncing in the settings so I deinstalled PS and installed the Version 22.1.1. Now PS is working again.
My system: MacBookPro running Windows10, 16GB RAM
i have the same issue 😞
First solution (verified)
Thanks to Peter-B who shared a solution provided by a Adobe employee in another thread, here's the first fix (works for both Windows and MacOS) :
Second solution (to be tested)
If, like me, you worry about the long-term fix and what causes the issue, I think I found it out. I reinstalled Windows two days ago. After reinstalling Windows, the memory leak caused by Preset Syncing option was gone. Today, I renamed my PC in Windows settings with the name I'm used to keep onto my succesive computers (and the name my computer had before reinstalling the OS). After restart, boom, the Preset Syncing option was back, as well as its memory leak. Ultimately, it seems that the option is tied to the computer's name. Changing back my computer's name to anything else caused the Preset Syncing option to be unchecked.
Thus, I would advise to try renaming your computer to see if the option is gone at PS launch. It may be preventing eventual future bugs with the Preset Syncing option forced to off via the first solution, as with this solution you simply simulate a new computer towards Creative Cloud.
Thanks! Worked for me.
Thank you. Works for me too.
First solution work for me!
Save my life!!! 🙂
First solution worked for me. Thanks for sharing.
This worked. Thank you!
Worked for me too, thanks !!!
So great, thanks so much, where wasting hours before i found your article. I had just on my MAC the Problem, not on my Windows PC so it was even more confusing - same Version, different Problem by same issue, thanks 😊
Thank you so much! After 3 un- and reinstalls I was starting to despair.
Thanks for this!
Problem still present at version 22.3 though...
Yep, true! And we againg have to add this txt file to be able to use this buggy Photoshop.
I tried this on a Mac on the latest Photoshop version (22.3) and it doesn't work. The only solution I found was to reinstall the 22.1 version which does not have this stupid preset sync feature which drains all the RAM and messes the whole computer up! WTF IS ADOBE DOING? How can you guys release a new version and still not fix this kind of stupid bug?!
It did work for me on 22.3 but I am on OSX Catalina 10.15.7 though...
But I agree that this is anoying indeed, still not as horrible as the liquify artifacts they did not fix for a very very long time..
Try solution 1 of Little World of Photo. It has worked for me with version 22.3
I already tried it but it doesn't work.
A thing to check might be that the PSUserConfig.txt you used was not converted to plain text?
As then Photoshop can not read it even if everything seem to be done as @Little World of Photo described in solution nr1.
This should work for everyone if photoshop indeed hangs on preset syncing like @Little World of Photo said, as it forces Photoshop not to use the function before it even starts.