Benches macOS

15

Mojave causes Photoshop CS5 to crash. Mac…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Ever since upgrading to Mojave, Photoshop CS5 crashes immediately after opening and generates the "Photoshop quit unexpectedly" error message.

The MacWorld fix (checking the Adobe Photoshop box in System Preferences under Security & Privacy and the Accessibility tab) did not solve the problem for me. Photoshop continues to crash a few seconds after starting. I don't even have a chance to open a file, it just crashes.

Any ideas on how to resolve?

  • iMac (Retina 5K, 27-inch, 2017)
  • 4.2 GHz Intel Core i7
  • 16 GB 2400 MHz DDR4
🔧 Closest iFixit match: iMac Intel 27" Retina 5K Display 2019-2020
Take-apart guides & videos on iFixit →
Double-check this is your exact model before ordering parts.

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    Eau Rouge

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Did you restart your Mac after applying the System Preferences> Security & Privacy> Accessibility 'fix'.

    Have you ever installed the Legacy Java Runtime SE6, if not download it from here,

    Download Java for OS X 2017-001

    once downloaded, double-click to install, then Restart.

    Also have a look to see if Photoshop CS5 is set to run in 64 bit mode. Open the Applications folder, click on the Photoshop CS5 folder from there highlight the Photoshop CS5.app, press Command- i to get the info panel up and make sure Open in 32bit mode is unchecked.

  2. 0

    Brandon Wilcox

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Eau,

    1. Yes, Mac was restarted (daily) after applying the System Preferences> Security & Privacy> Accessibility 'fix'.
    2. Legacy Java Runtime SE6 is installed.
    3. Photoshop CS5 does try to open in 64 bit mode. My applications folder info window doesn't look like yours so the clue to Photoshop trying to open in 64 bit mode is the splash screen that shows "Version 12.0 x64".
    4. For reference, here's what my info window looks like...

    And here's the Photoshop crash report I get each time I try to open it...

  3. 0

    mackee5223

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This is what worked for me:

    1. Do the permission / security settings as mentioned above.

    2. Open photoshop and try to go into preferences > type before it crashes. This might take several trys, but try to navigate there as quickly as possible. I was able to eventually get there fast enough (I've successfully done this on 2 different computers).

    3. When you reach the 'Type' options uncheck 'Font Preview Size'. I believe you won't be able to preview font's in the characters window anymore, but it's better than not being able to open Photoshop at all. 

    Hope this works for someone else. 

  4. 0

    Fedir Kurlak

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have exactly the same problem. Same info window without the Open in 32-bit mode check-box. Has this been resolved anywhere else? This is so frustrating. I have a further iMac and laptop and will definitely not update to Mojove. Surely there must be a fix that apple can come up with. (Everything else is as per instructions above: java updated, restarted, allowed PS under security & privacy but i cannot get beyond the "update java window constantly popping up when i click on PS. Come on apple - please rectify this problem quickly!!!!

  5. 0

    arinky-dink

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    HI. I JUST LITERALLY SOLVED THE PROBLEM (and I hope it helps you too!)

    When you open up the PS settings (Applications > Open up CS5 folder > highlight CS5 icon and click Command+i), click the little lock to enable editing the settings, scroll all the way down to "Sharing & Permissions:", on "everyone", change from "Read only" to "Read & Write".

    Exit that junk, open up PS again and HOPEFULLY IT WORKS AGAIN LIKE IT DID FOR ME. Otherwise, you'll have to turn your wallet into a murder victim because Apple products is designed to break.

    I really hope this helps though.

  6. 0

    Kurt Lang

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It's rather amazing that solved anything since that isn't even close to what those permissions are for. When you mark anything Read/Write in permissions, the only thing that means is anyone can delete that item, write to it, etc. It has nothing to do with the app itself being able to write data.

  7. 0

    Fedir Kurlak

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for all the feedback. Unfortunately the read-write solution didn't work for me. Whilst I appreciate Kurt's comment that there isn't much to answer, and VikingOSX's post illustrating that CS5 is not supported, it is nevertheless extremely frustrating that Apple can just turn off the lights to what was a very expensive piece of software. I realise that I can now go to adobe and shell out approx £50 per month for the latest Photoshop and Indesign but why is this deemed to be acceptable when the software that I had worked perfectly well for my needs prior to the Mojave update. I don't need the latest tweaks (which i probably wouldn't use anyway) and I wouldn't have updated to Mojave if I'd have been warned that any software pre-xxxx year would be rendered unusable. There is something very unethical about this If everybody's seven year old car suddenly stopped working and was rendered useless because a software update there would be a public outcry. But here, we are supposed to just say, "ah well...".

    I would be grateful if the Apple moderator could justify why it was impossible to make an allowance for 32-bit software to function within the Mojave OS and whether this is being looked into.

  8. 0

    Kurt Lang

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Apple didn't turn the lights out on anything. It's ancient software that Adobe stopped supporting a long time ago. CS5 was released in 1990. You did get your money's worth out of it the past 29 years, haven't you?

    A moderator can't do anything about how Apple is changing the OS. The entire concept of 32 bit software is being relegated to the dustbin of history, along with many, many other items from the relatively short time personal computers have existed.

    Windows is also, eventually, going all 64 bit. I read somewhere that Windows 10 may likely be the last version you can get as 32 or 64 bit.

    From a technical standpoint, having a mixed system is a headache for engineers, and makes the entire system more prone to crashing. Memory addressing in particular is a problem. Let's say Photoshop CS5 grabs 4 GB of the 8 GB of RAM you have installed (I don't know in particular how much RAM your Mac has. This is just an example). Because the RAM allocated to CS5 is blocked out for 32 bit addressing, a 64 bit app cannot touch it. You cannot manage two types of memory addressing in the same block of RAM. Likewise, a 32 bit app cannot use any RAM allocated as 64 bit. Doesn't matter how much is being taken up by an app that's running, but sitting idle. Until you quit the app, nothing else can use that space.

    Having everything as 64 bit makes it much easier for the OS to allocate RAM dynamically to any app that's requesting it. It doesn't have to wait for you to quit a 32 bit app in order to access some of the RAM that app is holding onto.

    Computers move forward all the time. This is just another step.

  9. 0

    Fedir Kurlak

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks Kurt. I don’t dispute your knowledge - you clearly know what you are talking about. I am not sure about the 1990 though. CS5.5, which is what I have, was released in 2011 which is when I bought it. Had it been 1990, I wouldn’t be complaining and I wouldn’t have used the 7 year-old car analogy.  

    I’m using 16GB memory on my iMac and the CS5.5 ran as smoothly as soft butter to bread.  The system didn’t crash once and I certainly put it through its paces with InDesign and various other programmes working at the same time.  

    I don’t disagree with the argument about progress but we should all be careful of what we wish for.  If this example of progress (blanking out some 7 year old software) is allowed to replicate itself year on year, we’ll all be left with a bundle of totally useless software/hardware and having to shell out more and more to update to 128-bit, then 256-bit, followed by 512-bit apps.  And those “old” jpeg photos too will probably soon become unreadable because they will be deemed to be holding up new technology…

    Common sense ought to prevail amidst the clamour to be faster and more dynamic,  Most of us are just normal people who cannot go out and buy a new computer every year or subscribe to ever-changing new software.  There needs to be a differentiation between normal users that are happy to work on existing (perfectly good) software and the big businesses that are hungry for the super-highway stuff.

    I know that you will probably disagree with me but we are all entitled to our views.  I was and am a big fan of Apple and I still think that they should answer my questions. Otherwise, how am I (and all other apple users) to know whether my scanner, printer or OCR software will suddenly stop working after the next OS update in the name of progress?

  10. 0

    Kurt Lang

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You are definitely correct, there. I put in a Google search for "cs5 release date". The first thing that came up was 1990. I should have known that was wrong. Well, it's right if what you were looking for was the very first release of PS.

    Yes, CS5 was 2011. Still old for just about any software title.

    I'm not really disagreeing with you. But it's a given with software. Developers can't stay in business by forever supplying free updates for apps you've purchased. They stay in business by getting you to buy a newer version. I've lost count of how many apps I've purchased over the decades that can no longer be used.

    You do, however, have another option. Get the free virtual machine software, VirtualBox. Install an older version of macOS within that which CS5 is compatible with. Such as Yosemite (if you have older versions of OS X in your App Store account you can get at). Then install CS5 in Yosemite and run it from the VM.

    You will need a good amount of RAM installed. Bare minimum of 16 GB to reasonably run Mojave, and yet another OS within the VM. And you need to assign enough of your Mac's RAM to the VM's virtual video card so it runs at a higher resolution than 1024 x 768.

  11. 0

    Brandon Wilcox

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sorry Kurt but you are out by 20 years. CS5 was released on April 30, 2010 and CS5.5 on April 12, 2011. I agree with Fedir that it is not unreasonable to expect a very expensive piece of software to keep working and not be rendered obsolete in such a short period of time. I am very pro progress, but I deeply resent being forced into Adobe's exorbitant subscription service for features I don't need just because Apple took the easy route, i.e. avoided the engineering headache of a mixed system. Good for Apple's profits; bad for Apple's users.

  12. 0

    Kurt Lang

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Already responded to the incorrect date.

    What's unreasonable? To whom?

    I also greatly dislike Adobe's high monthly cost just to keep the software functional. But, I also make far more than that per month using it in my small business. It's just part of my operating expenses to be able to seamlessly send files back and forth with my clients.

    I do get how Adobe came up with that price, though. The boxed upgrades used to come out in (roughly) this cycle: 2 years - 1.5 years - repeat. Since you have access to every app with the CC Suite, this is similar to always purchasing the Master Collection each time an upgrade came out. That typically cost $1200. So, 24 months times the monthly subscription fee of $53 equals $1272. You're paying the same thing you would have for the boxed upgrades. This does assume you always upgrade, as we did. We had to because because our clients did, and still do. It comes back to a necessary expense for us.

    What's to dislike, then? That's easy. The many, many users who can't afford to upgrade every new release, or need to. But that doesn't change that older software stops being supported. No support, and it eventually doesn't work. Adobe can't be singled out for that since it's the same for literally any piece of software you can obtain. It's just the cost of this particular software that irks people. A $20 that stops working after 8 years isn't a big deal. You upgrade for another $20 or so without thinking about it.

    I use MS Office for same reason. Sure, I could easily do everything I personally need with the free LibreOffice or OpenOffice, but neither can perfectly open any MS Office you may get. Uncompromising compatibility comes ahead of free.

    How is the switch good for Apple's profits? For Apple in particular, that is. No one is forcing you to purchase the latest 'n' greatest computer, or upgrade the OS if what you have suits your needs.

  13. 0

    Kurt Lang

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Independent. Like virutally everyone here, I'm just another user. The only Apple employees you'll see in these forums are the Community Specialists (they have a gray Apple icon). And once in a blue moon, a moderator will post in the open forums.

    Not that there may be a number of Apple employees who come here on their own time. But they're not supposed to announce it.

  14. 0

    lifeonfilm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have this exact same problem. I actually haven't rebooted in weeks and finally did today to clean some things up and now I can NOT even click on a file once it's opened in Photoshop CS5.1 while running the current updated version of Mojave. This is EXTREMELY frustrating as I'm not into cloud based services so absolutely do not want to pay a monthly fee to access a program I already own. I understand all of the updates and fonts and blah blah blah but to me CS5 should work. For those of you who say "It's sooo old", it came out in 2010, it should be fully compatible with any operating systems moving forward.

    None of the fixes suggested have worked and I have tried them all.

  15. 0

    VikingOSX

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    VirtualBox v6.0.4 still supports the same amount of guest VRAM as the product supported ten years ago — 128 MB. That is the maximum that the user can assign via the user interface settings. One can double that amount (but no higher) from the command-line:

    VBoxManage modifyvm Win10 --vram=256

    VirtualBox will use the hardware GPU of the host, and that is especially noticeable when a discrete GPU is available.

    The other thing to realize is that even at this late stage, VirtualBox v6.0.4 does not provide Guest Additions for OS X/macOS guests, so you are stuck with an 8 inch square window in the center of the screen, instead of the full screen at 1920x1200 that for instance, Ubuntu 18.04 or Windows 10 1809 receive. Until Oracle gets a grip on the future, and implements proper guest addition support for Mac operating systems, I certainly can not recommend it for that purpose.