Skip to main content
Participating Frequently
May 4, 2012

P: CS6 beta crashing on my system (Win, more than 4 scratch disks)

  • May 4, 2012
  • 44 replies
  • 698 views

Photoshop CS6 beta is... the most unstable version of Photoshop I've used in the past ten years.

Drag and drop a file? Crash.
Export to PNG? Crash.
Use Liquify? Crash.
Use Iris Blur? Crash.
Do nothing at all? Crash for no reason at all.

And already on a big job with a VERY tight deadline, upon momentarily closing two PSDs I'd spent five hours a piece on, I tried to open the files again for comparison and they were both corrupt. I did nothing whatsoever- only saved and closed them- but Photoshop CS6 corrupted both to the point where I couldn't reopen them in any version of Photoshop. It's gotten to the point where I simply cannot use the program at all, and hope things are fixed in the actual release. Ten years I've been using Photoshop with not a single hitch, and now this beta is simply monumentally broken.

If you know ANY way to fix the stability- whether it's a reinstall or whatever- PLEASE let me know. I'm using CS5 in the meantime but I'd love to take advantage of all of the improvements in CS6.

Please help.

This topic has been closed for replies.

44 replies

Inspiring
October 23, 2012
BTW - Apple believes they have fixed these issues in MacOS 10.8.2.
Legend
October 23, 2012
This issue should be fixed in the 13.0.1 update: http://adobe.ly/PS-Up-To-Date
Inspiring
May 23, 2012
This topic is discussing a specific problem with Photoshop - not Bridge. Please create a new topic to discuss your problem in Bridge.
May 23, 2012
I've had a similar issue with CS6/Bridge. Here's what I've found so far.

If I start my computer (Win7 64 bit) and load CS6/Bridge, it works fine. If I close CS6/Bridge to do something else and then attempt to reload CS6/Bridge, it loads CS6 but freezes when trying to load Bridge. I've found two temporary workarounds.

1) Cold reboot the computer and all is OK.

2) If you are trying to re-load CS6/Bridge on a computer without rebooting, you can open the Windows Task Manager - Processes tab and you'll see that Bridge is still loaded. For some reason, when you close CS6, Bridge is not unloaded from the OS. Terminate the Bridge process in Task Manager and CS6/Bridge will load and run normally.

I think there may be a lot of 'red herrings' in the above posts that are off track. Try this and see what happens.
Inspiring
May 20, 2012
The version of Photoshop doesn't matter - you appear to be crashing in MacOS code, and that could affect any application.
Participant
May 19, 2012
I uninstalled CS5, reinstalled CS6 and ran disk repair... didn't fix it. so, basically I can't use Photoshop CS6 if I want to SFW?
Participant
May 19, 2012
it's crashing in the save dialog. I'll run repair in disk utility and delete the CS 5.5. do I need to reinstall CS6 after I delete CS5.5? does deleting it work or do I have to figure out how to uninstall?
Inspiring
May 19, 2012
Oh, if you crash in the save dialog (not while writing the file), then you may be hitting one of the MacOS file system bugs (FinderKit), or the open/save dialog UI bugs (appKit). Running Repair in DiskUtility usually solves the FinderKit problems, but there are no known workarounds for the bugs in AppKit. We've sent those crash reports to Apple and are waiting for OS bug fixes.
Inspiring
May 19, 2012
MacOS does not have the same limitation for the number of scratch volumes.

You're looking at something else.

And we have very, very few crashes for SFW or the file formats. The few I've seen resulted from someone loading CS5 plugins into CS6 by mistake.
Known Participant
May 19, 2012
Brenna, I wonder if your problem is with the CS updating. Did you (or could you on OSX?) update an existing CS version or remove it completely and then install the new version? On my PC I sometimes find it best to remove the old version first and clear out its files including settings/preferences. Installing the new version then requires you to enter the old vers serial number first of course. I did this when going from CS5.5 and CS6 Beta to CS6 retail to get a clean install.

Just a possibility unless there really is something in CS6 that is faulty for some systems and not for others.