Mojave causes Photoshop CS5 to crash. MacWorld fix doesn't work.

Hello? Is anybody listening?

At minimum, the users who've already posted in this topic are likely reading your responses. But without an idea of what to tell you, there isn't much of a reason to answer.

This worked great, I have tried all the other things with no luck.when I went back the setting put itself back to write

but still working.trythis

Kurt, You put up a good argument but let me just clarify before I answer further, are you representing Apple here or are your views totally independent?

Thanks Evan-e-cent, this logical fix finally worked!!!

Nice one arinky-****. Realising I'm resurrecting a fairly old post here but I had this issue, tried your solution - worked a treat. Many thanks.

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.

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.

This is a guess, but it seems to me the real problem is how much the OS is getting locked down. Each release since El Capitan gets more and more protected at the system level.

CS6 and earlier didn't have this to deal with when they were released. This means they expect easier access to the main Library folder and the computer's system resources in general, but no longer have such unfettered access. CS6 still works (at least we had no trouble running Photoshop CS6 in Mojave). But you do have to give the app extra access under the Privacy tab in Security & Privacy of the System Preferences in order for it to behave correctly.

At nine years since its release date, CS5 is simply old (CS 5.1 is eight years old). In computer years, that's a lot. Complex apps like this are typically going to fail before simpler ones.

Thanks for the feedback. It appears to be a memory issue. CS5.5 wasn't allocated enough memory and the last item on my list should help a lot of people:

PhotoShop > Preferences > Performance > Allocate almost all the RAM memory to PhotoShop.

Allocating all your RAM might sound dangerous, but it will not run out of memory because the Mac uses virtual memory ie moving stuff that is not being used from RAM memory to the hard drive. This frees up space to run other programs without losing the information that PhotoShop was using in RAM.

Disabling all the plugins also served to free up some memory.

I don't have the "Open in 32-bit checkbox" .. in the information window.

Where can enable it?

You highlight the main Photoshop CS5 app and do a Get Info on it.

Here is the RoaringApps story on Photoshop CS5. It is toast on Mojave. Neither Adobe nor Apple are going to fix this years unsupported software.

Setting the app info to everyone read and write from read only under info worked for me