Skip to main content
Participant
May 2, 2010
Question

CS5 Crashes on Quit

  • May 2, 2010
  • 19 replies
  • 33435 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.

    19 replies

    Participating Frequently
    June 4, 2010

    I am having the same problem with CS5 and am not a "techie".  I get the "Photoshop Closed Unexpectedly" message every time I close the program. I have tried uninstalling and installing with no solution.  I have executed the "fix permissions" and there does not seem to be an error.  Have you found a solution?   Thank you for your help.

    Participating Frequently
    June 5, 2010

    Reply to Susie David

    It will speed Adobe's help to you if you can add some pertinent information.

    What CS5 product are you using? There are many different 'packages' and they need to know that.

    Is this an upgrade or is this the first CS product you have purchased?  if an upgrade, from what package, CS5 Design Premium? Other?

    And, very important, what computer are you using and what is your present operating system.

    Adobe Tech Support is under a lot of stress because this is a common problem and it will speed their help to you with those answers.

    Good luck!

    hoyhoy
    Participant
    June 10, 2010

    The CNET article was right.  However, on my installation, the following directories seem to be the ones with incorrect permissions.

    chmod -R u+rw ~/Library/{Preferences,Application\ Support,Adobe}
    chmod: Unable to change file mode on /Users/jperrie/Library/Preferences/Adobe/Extension Manager CS5: Operation not permitted
    chmod: Unable to change file mode on /Users/jperrie/Library/Preferences/Adobe Photoshop CS5 Settings: Operation not permitted
    chmod: Unable to change file mode on /Users/jperrie/Library/Preferences/ExtendScript Toolkit: Operation not permitted

    So, I think the only real fix required is this:

    sudo chmod -R u+rw ~/Library/Preferences

    Tony

    http://involution.com

    Participant
    May 28, 2010

    I've had this problem also, I can't seem to get it to fix itself... so I'm going to reinstall it.

    Participant
    May 28, 2010

    Use the control + click the adobe cs5 app. That should do the trick.

    Participant
    May 28, 2010

    The solution that worked for me:

    1) Open Terminal

    2) cd ~/Library/Application Support/Adobe

    3) sudo chown -R YOURUSERNAME .

    4) cd ~/Library/Preferences

    5) sudo chown -R YOURUSERNAME .

    Replace "YOURUSERNAME" with... well, obviously with your own username.

    You need to enter the admin password after the sudo command.

    After this, no more crashes and Preferences get saved as well.

    Note: it changes user ownership to yourself, which all the files in those folders

    should be anyway.

    For some obscure reason the Adobe CS5 installer creates the default user

    preference folders with the Admin permissions instead of the current user

    permissions. Fix that, and your problem will be solved.

    Cheers,

        -Andreas F. Bobak

    -- 
    AfB Studio GmbH · Trittligasse 4 · CH-8001 Zürich · http://www.afb-studio.com · MwSt 566 449

    Participating Frequently
    May 21, 2010

    Chris,

    I fully understand what you are saying.  However, in my case, my statement about this installation taking your entire system down is not an over-exageration.  I am still rebuilding my system for the second time.  The first time I had CS4 Master Collection in my system and all permission mumbo jumbo, along with the attempts to fix the permissions, managed to not only lock out or make unusable many of my programs, it also put a lock on my RAID drive inside my Mac Pro.  No one anywhere had an explanation and none of the Apple or third party software I tried could unlock it.  The only solution was to destroy the RAID and start over, which I did.  I even put in a brand new hard drive for my OS and Aps.  After getting all the updates on the new fresh OS install (10.6.3), the only program I put on the system is Master Collection CS5.  The very first use of Photoshop, I get a crash report.  So, I do not believe any of my statements are over-exagerated.  I cannot image a virus, a worm, or a trojan causing more damage.

    Fingers are crossed that you have your engineers working 24/7 to get this figured out and a fix sent out ASAP.

    Thanks and please share any updates the minutes you have information.

    Participating Frequently
    May 21, 2010

    Just spent a day installing a new drive in my Mac Pro for the OS and Aps.  I updated everything and eventually installed Master Collection CS5 without anything else on the drive with the exception of the ability to connect to the internet.  Upon opening and closing PS CS5, I still get the message that Photoshop CS5 has crashed. 

    Apparently, this has nothing to do with having CS4 previously installed on our systems and I am about as angry as I have ever been in my life. This is complete garbage for software.  I think Steve Jobs really knows what he is taking about when he addresses Adobe's ability to handle software development. Sorry if that is seen as an insult.  As this point it is intended as both an opinion and an insult.  To anyone considering CS5 as a buy....don't!  You will regret it as it will trash your system from top to bottom.  Maybe months from now as all of us as customers have identified all the things that should have been identified and fixed in Beta testing are fixed, it will be worth something.  Right now it is an albatross that will take your system into unusable territory....also known as junk software.  It would be hard to imagine a virus, netbot, trojan, or anything else developed by the scum that do such things that would cause more damage to a user's system.  Is this worth the $2500?  What do you think I think?

    Chris Cox
    Legend
    May 21, 2010

    You will regret it as it will trash your system from top to bottom. 

    I agree, the installers shouldn't make the mess they do.

    But gross and irresponsible exaggeration of the problem won't help.

    The installer do sometimes mess up the permissons on some Adobe specific directories.

    They don't do anything to most of your system.

    The only things they can "damage" are the Creative Suite apps.

    And they are still working fine for 95%+ of the users.

    We're hounding them to get a fix posted.

    But, again, exaggerating the problem and trying to scare other users is not going to help anything.

    Murseblonder
    Known Participant
    May 20, 2010

    ... sorry to disturb ... just another of those guys sending error reports by the dozen. Fixed permissions single handed on each and every possible file affected. First got PS running, then Illustrator.

    Uninstalling and reinstalling, even with the cleaning tool, didn't do the job. Only the permission thing worked, and only manually. Using the mentionned batchmod-way didn't solve all the problems for some reason or another.

    Self using OS 10.6.3. / Mac Book Pro 3.06 Ghz 8GB

    Was happy to be on Mac so far, not having to use the PC crap. This workaround cost me more than the new software ... any chance to deduce that from income tax?

    Participating Frequently
    May 19, 2010

    Well, looks like I'll be one of the "sit back and wait for the fix" types since I'll spend the next two days rebuilding my system since this entire mess has trashed it top to bottom.  I'll be watching the mailbox for a new set of CS5 Master Collection install disks sometime down the road.  This time, I'll wait a week or so to see how the new set of installation disks works for others before being a "guinea pig."  There are several features I really need in CS5, but the lost time can never be made up.  As an engineer and developer, I've always followed the rule of not being the first to jump on a new product...until now.  Man, I hate it when I have to tell students and coworkers how stupid I was to not follow my own advice.

    I don't mean this as an insult, because I agree that insults will get us nowhere in solving the problem.  However, how can something this big sneak by 5000 users (beta testers?) over year and a half and not be isolated?  Something doesn't jive. 

    Chris Cox
    Legend
    May 19, 2010

    However, how can something this big sneak by 5000 users (beta testers?) over year and a half and not be isolated?  Something doesn't jive.

    Read what I said.

    After beta testing is completed, the installer team finalizes things for the suite installers.  Somewhere in that process (AFTER beta testing), this bug was introduced.

    rfranssen
    Participating Frequently
    May 19, 2010

    Yes I read what you said:

    Somewhere between beta testing and your loyal users Adobe f*cked up. Now don't take that as an insult. I'm using the product right now. Everything is working and I'm evaluating. Anyone that asks for my help will get it. Loosen up and if the shoe fits...

    rfranssen
    Participating Frequently
    May 19, 2010

    CS5 Upgrade Path:

    Well most of the struggle is behind me. This is a HUGE permissions clusterf*ck and there are some other significant let downs but hey, its Adobe!

    1. Use a utility such as BATCHMOD to change and repair permissions. These are the areas to work with but may not be limited to these alone. I did enable viewing hidden files and had my console close at hand to monitor the progress.

    • User/Library/Adobe
    • User/Library/Preferences < all Adobe Preferences >
    • Applications < All Adobe Applications >

    You will need to add the User/Administrator for your computer to the ACL list and then apply those permissions to all the enclosed items. That should allow all the CS applications to write the necessary files in the appropriate locations.

    But, you will lose your workspaces, your custom actions, styles etc. Those can be found in the CS4 (3) folders and copied to the corresponding CS5 folders. The Adobe Extension manager will allow you to import the extensions you have loaded from previous versions.

    I imagine that Adobe is letting us do a lot of the beta testing ourselves. Hey I only lost a half a day! Hooray...

    Solved on a Mac

    Participating Frequently
    May 19, 2010

    Franssen,

    You have earned a very enthusiastic note of appreciation for your detailed work. Alas, it's wasted on this old cowboy because the technical aspects of this mess are beyond my ken. In the "good old days" I was a programmer but the issues involved in 'service managers' and 'permissions' and using and repairing damage is just not possible. When you are 75 I hope you can still do it!

    The arrogance of a monopoly such as Adobe holds in the creative suite functions -- if history is consistent -- will attract competition sooner or later. It's already 'later' for me and I hope Google gets busy or another group and they take the trouble to coordinate the various elements of a new creative software package. That similar functions are treated differently in their commands as you switch from Illustrator's needs to InDesign and over to Photoshop and I can't tell you how nervous I am that one day I'll have to use Flash. Perhaps by that time a truly unifying concept will be in charge and the suite that results will be far more powerful with much less grief and probably be available for half the price to a waiting and friendly customer base. They might even give you a free copy for being a beta tester and I bet there are those on this board who think that's a new idea.

    There is possibly what seems to be competition between various groups, the constituency of programmers that 'owns' the different parts of the suites. That's why we have this problem with what should have been TASK ONE, thinking of successfully about installing the new code before you get too busy with the 'goodies' to take care of it properly and -- as a result -- the new stuff doesn't work.

    rfranssen
    Participating Frequently
    May 19, 2010

    OK new wrinkle. I've found this in the console log entry:

    5/18/10 7:09:41 PM [0x0-0x44044].com.adobe.flash[533] 2010-05-18 19:09:41 : ERROR vcfoundation::system::VCAccessDenied: open('logs/CS5ServiceManager_native.log', 1545) failed <13: Permission denied>

    Adobe has an application running in background called CS5 Service Manager and this is generating hundreds of errors for all their apps in the background probably causing the app hangs and crashes. It's is related to permission access to a log file. Just one other missed item during Adobe extensive beta testing on Snow Leopard. (OK, they didn't do a lot of testing, heck their are bills to pay and pockets to line.)

    Chris Cox
    Legend
    May 19, 2010

    (OK, they didn't do a lot of testing...)

    5000 users over a year and a half wasn't a lot of testing?

    Wow.

    This permissions bug appeared after beta testing was completed, and before we shipped the builds to customers -- sometime during the suite integration of the installers.   We're still trying to figure out what went wrong.    We have many people working on a short term solution, and on long term fixes.

    Stop with the insults and either help other users solve their problems, or sit back and wait for a fix.