Sample Header Ad - 728x90

Adobe Photoshop CS 5.1 not working in Mojave via Parallels

1 vote
1 answer
415 views
I am trying to run Photoshop CS5.1 (from the Adobe CS 5.5 Web Premium suite) in MacOS 10.14 Mojave using Parallels. The host machine is a 15" MacBook Pro late 2013 with a 2GB nVidia GT750M GPU and running Catalina. However, when I try to run the program it briefly flashes the splash screen then I get an error saying it quit unexpectedly. Here is an excerpt of the error: Process: Adobe Photoshop CS5.1 Path: /Applications/Adobe Photoshop CS5.1/Adobe Photoshop CS5.1.app/Contents/MacOS/Adobe Photoshop CS5.1 Identifier: com.adobe.Photoshop Version: 12.1 (12.1x20110328.r.145] [12.1) Code Type: X86-64 (Native) Parent Process: ??? Responsible: Adobe Photoshop CS5.1 User ID: 501 Date/Time: 2022-05-01 17:03:18.483 +0100 OS Version: Mac OS X 10.14.6 (18G103) Report Version: 12 Anonymous UUID: 34F192B4-EA33-C3C5-1CE6-A1D68E7455E1 Time Awake Since Boot: 110 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler VM Regions Near 0: --> __TEXT 0000000100000000-00000001026fc000 [ 39.0M] r-x/rwx SM=COW /Applications/Adobe Photoshop CS5.1/Adobe Photoshop CS5.1.app/Contents/MacOS/Adobe Photoshop CS5.1 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 com.apple.opengl 0x00007fff385c6d79 CGLDescribeRenderer + 78 1 com.adobe.Photoshop 0x00000001008ca245 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 6217217 2 com.adobe.Photoshop 0x000000010072d32d AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4525801 3 com.adobe.Photoshop 0x000000010073bd7b AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4585783 4 com.adobe.Photoshop 0x000000010073bf6c AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4586280 5 com.adobe.Photoshop 0x0000000100628f00 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3459772 6 com.adobe.Photoshop 0x000000010062a097 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 3464275 7 com.adobe.Photoshop 0x00000001006b4a45 AWS_CUI_GetVersionComments(OpaqueWindowPtr*, adobe::q::QDocument&, adobe::q::QString&, adobe::q::QAttributeList&, adobe::q::QDocument*, adobe::q::QProject*, long) + 4032001 8 com.adobe.Photoshop 0x0000000100236e15 0x100000000 + 2321941 9 com.adobe.Photoshop 0x0000000100237229 0x100000000 + 2322985 10 com.adobe.Photoshop 0x0000000100002294 0x100000000 + 8852 From this information I believe this is some sort of OpenGL issue resulting from running in Parallels rather than a general compatibility problem with this version of Photoshop and the OS. Numerous people have reported CS 5.5 mostly working fine on Mojave when installing from scratch, and I have already followed some documented steps to make it work: - Installed legacy Java runtime - Gone to system security settings and allowed app to control computer and have full disk access I also noticed that Dreamweaver works to an extent and this is probably due to it not being so reliant on hardware acceleration I already contacted Parallels support by email and their suggestion was to increase CPU and RAM allocation, but the VM already has 2 CPU cores and 4GB assigned. I could maybe try using an older OS for the VM but I don’t want to risk wasting a load of time without knowing if it will work any better. If anyone has encountered similar problem and found a workaround please let me know
Asked by James (85 rep)
May 1, 2022, 08:06 PM
Last activity: May 2, 2022, 11:37 AM