Participant

Question

CS5 Crashes on Quit

Forum|Forum|15 years ago
May 2, 2010
19 replies
33436 views

Has anyone else seen this and found a solution?

Installed CS5 Standard, OS 10.6.3, MacBook Pro 4,1

When first installed, I could not change prefs - as discussed in thread:

http://forums.adobe.com/thread/628368?tstart=0

I manually changed permissions. CS 5 will now launch and operate. When choosing "Quit" CS5 closes all windows normally, however the menu bar does remains and the spinning beachball displays. After about 20 seconds Mac OS reports that Photoshop quit unexpectedly. A minute later Adobe's crash reporter appears.

I've uninstalled and re-installed.

Stephen

This topic has been closed for replies.

Show previous replies

V

VideoBuddy

Participating Frequently

It gets worser and worser (and yes, I do speak English). I fixed the permissions problem by following the instructions provided in this thread. The good news is PS CS5 will now open and close properly and it recognizes my Nvidia GTX 285 Video card as being adequate as a GPU for working with PS CS5. The bad news is the permissions fix also locked me out of my three disk RAID attached to my Apple RAID card, which just happens to be where all of my audio, video, and photographs are. I have the same question you are now asking, "How can that possibly be true?" So far, Apple's only solution to fixing the problem is to trash the RAID and rebuild it. They have never seen anything like this happen before. Disk Utilities and RAID utilities see the disk and everything I run on it says everything is OK, but there is a small "lock" icon on the disk icon and it will not allow me to see what is on the RAID disk. I suppose this problem could get worse, but I'm having a hard time imagining how. I will probably start all over tomorrow and rebuild everything from scratch. Something tells me this version of the Creative Suite was not fully vetted and beta tested. We are at least part of the beta testers and I'm about to lose dozens of hours rebuilding everything to add to the many hours already lost in this mess.

H

Hawaii_Bill

Participating Frequently

Even at my modest hourly rate, I've wasted more billable time fixing CS5 than it cost for the "upgrade."

These forums seem to be the only way Adobe has found to be notified of problems but they are insufficient when most of the acknowledged problem fixes came from other customers. Or am I missing something, Chris?

Chris Cox

Legend

Or am I missing something, Chris?

Yes, you're missing the many employees posting fixes and working with customers to diagnose the problems. (some of whom failed to get employee labels on their AdobeID account)

Technical Support is also gathering reports of problems, and possible solutions.

User submitted bug reports also help, when they include contact info so we can get in touch and help solve the issue.

The crash reporter system is gathering data, and we have created bug reports from those and assigned them to engineers to investigate.

You're seeing less than 5% of the troubleshooting going on.

rfranssen

Participating Frequently

Hey Everybody,

Let's focus on this first. How the hell can Adobe miss this after ALL THE YEARS THEY HAVE BEEN RELEASING PRODUCTS FOR OSX!!!

Unforgiveable...

Now to the first solution for the inherent problems with the installation, more to come on the problems within the applications later.

Fix the permissions on the Library/Application Support/Adobe, User/Library/Application Support/Adobe, User/Library/Preferences and User/Applications by selecting the folder itself, adding your user and allowing read/write permissions and then Apply to Enclose Items

This will change the permission for all items that Adobe somehow missed if they beta tested on anyone's system before release...

Really poor programming and customer support.

H

Hawaii_Bill

Participating Frequently

Can anyone tell us if Adobe is a.) aware of this problem and,

b.) doing anything about it and,

c.) the schedule for getting CS5 back to expectations?

Thank you

Chris Cox

Legend

a) and b) - read the existing posts in the topic

c) nope, not yet.

A

Anonymous

I had all these errors and crashes, and I have been using Photoshop CS5 for a couple of days now with no problems, starting and quitting many times. MacBook Pro 10.6.3. Here's what I did:

* Uninstalled Photoshop CS5 and all previous versions of Photoshop. Used the appropriate uninstall programs -- did not rely on dragging files to the trash. I had saved a copy of my former Presets (brushes, actions, etc.) that I wanted to use with the new version.

* Created a new Test user account. I left the password area blank; kept it simple. If you don't know how to do this, here's how: http://docs.info.apple.com/article.html?path=Mac/10.6/en/8235.html

* Logged out and logged in as Test user.

* Installed the program from the CD within the Test user account. Made sure to install it in the system-wide Applications area (under the name of your hard drive) so it can be used by any user on the computer.

* Used Get Info to change permissions on all the Adobe files and folders listed by another writer above to Read/Write for Everyone.

* Opened PS CS5, created and saved a new document size preset, put some type into a dummy document, saved the doc.

* Quit -- no crash.

* Reopened program; document and preset (a change to preferences) had been saved.

* Logged out and logged back in to my regular user account.

* After another fine start and quit, I moved all my former brush folders and actions into the CS5 Presets folders.

* Everything has been working fine ever since.

H

Hawaii_Bill

Participating Frequently

Thank you clstern for that good detail. Seems very different from the instructions passed along by Adobe.

I've been noticing a lot more problems from folks using Snow Leopard than I see from old Leopard where I'm still parked.

Wonder if there are some internal CS5 differences with Leopard 10.5.8 a few different problems to go with them.

D

davisdont

Known Participant

Hawaii Bill wrote:
Thank you clstern for that good detail. Seems very different from the instructions passed along by Adobe.
I've been noticing a lot more problems from folks using Snow Leopard than I see from old Leopard where I'm still parked.
Wonder if there are some internal CS5 differences with Leopard 10.5.8 a few different problems to go with them.

i'm hoping there'll be some improvement with the graphic driver update in 10.6.4. 10.6.3 seemed to make alot of open gl stuff unpredictable and i found in the past that gpu freakyness in general would make cs4 unstable

B

bizcheers

Participant

you may check here

http://driverscat.com/photoshop.aspx may help you out

V

VideoBuddy

Participating Frequently

Like everyone else on here, I'm getting the same error and crashes with PS CS5 on Mac Pro with 32Gig of RAM. Please send us a fix ASAP. As of right now it is useless software we have paid for.

Chris Cox

Legend

Please read the existing answers before posting.

You didn't even tell us WHICH error or crash you're seeing.

V

VideoBuddy

Participating Frequently

I've read every answer before responding. Why the hostile response?

PS CS5 says my Nvidia GTX 285 card doesn't meet minimum standard and

will not do Open GL/CL, yet It is listed as meeting standards on the

Adobe requirements.

It says it cannot save my preferences and Open GL is grated out. It

then crashes and says it can't save my preferences. I'm just trying

to get my $2500 investment in CS5 Master Collection to work.

I appreciate any help you can provide but don't be hostile to those

seeking solutions.

Thanks,

Dave

D

dmarkman

Participant

it looks like adding myself to the sharing/permission and giving read/write permission for

~/Library/Application Support/Adobe/CS5ServiceManager

fixed the problem

S

Stephen StarkmanAuthor

Participant

Got it running.

Work around:

- uninstall Photoshop CS5 using Uninstaller

- create new user account with admin privs (temp account to install Photoshop)

- log on to new account, install Photoshop CS5

- run Photoshop CS5 to test if there are any issues (none in my case)

- log off temp account, log on to original account, delete new user account

- test, done.

D

dorenseanmichael

Participant

Hi,

I tried the Uninstall/Install Temp Account User method, but it did not work for me. CS5 Photoshop still crashes/hangs on quit. Any other suggestions?

Thank you,

-Doren

Chris Cox

Legend

No more suggestions right now. Folder permissions is the one cause we know about.

I'm still looking at all the crash reports for more clues.

I've managed to reproduce one other crash on quit myself - but it's one that very few people have reported.

But we've got several people looking into these issues.

D

davisdont

Known Participant

hi, i changed the permissions with the finder but it didn't work on all the nested files for some reason..i fixed it with batchmod.app which you can find on versiontracker or macupdate (i'll assume i shouldn't post a link). i fixed the user/library/permissions folder and the user/application support folder

Chris Cox

Legend

Send in the crash report with details (what did during the session, what troubleshooting you might have done, etc.).

I'm looking at all the crash reports.

S

Stephen StarkmanAuthor

Participant

Hi Chris,

Yes, I've sent in the report - Adobe Crash Reporter.

Here's the chronology:

- installed Photoshop CS5, no errors reported

- could not enable GPU or change prefs. When quitting, CS5 reported:

"Could not save Preferences because the file is locked or you do not have the necessary access privileges. Use the ‘Get Info’ command in the Finder to unlock the file or change permissions on the file or enclosing folders."

Manually added/changes permissions as per the "Locked" thread on this forum

http://forums.adobe.com/thread/628368?tstart=0

CS5 would now allow GPU and changing prefs, however upon choosing "Quit" it hangs with the spinning beach ball then OS reports "unexpectedly quit".

That's where I am now.

Update: installing CS5 on a Mac Pro running OS 10.6.2 (not the 10.6.3 which is having the problem) - CS 5 installs correctly and works properly without any modification.

Thanks again!

Chris Cox

Legend

Without seeing your exact report, I'm going to guess that it's a crash in ServiceManager because of bad permissions on a different folder. (we've got several crashes because of that)

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded