[BUG]: [Regression] Older Intel Macs: Crash on launch after v1.7.5849 (Memory Map failure) #11728
Comments
|
Maybe the MAC build isn't universal or using ARM only features/flags? Working here on M1 Max. Sonoma 10.16.1 I don't have any games to test on mac, but it starting UI perfectly fine. |
|
I can confirm that #11734 fixes this on my 2015 MBP 👍🏼 |
Excellent - have you run this on a self-compiled version with the patch/change included? |
No, I used the CI build from the GitHub action for this PR. |
|
This fixes the issue for me. MacBook Pro 2012, OCLP, Sonoma 14.6.1. |
|
BTW the same change in Duckstation lets it crash too. The build before "use mach routines for VM mem ... something" works. |
|
Tested versions until latest nightly 2.3.66 and confirm not working ( Intel i5 Macbook pro 2015, 16gb Ram, MacOS Sequoia; Intel Xeon x5690 Mac Pro 2010, 32gb Ram, RX580 8Gb Vram, MacOS Sequoia), same error occurs and app crashes instantly. Version 1.7.5847 works well in both computers. If you need help testing any version, would gladly do so. |
Describe the Bug
PCSX2 crashes on launch on older Intel Macs with the following error message:
Failed to map data memory at an acceptable locationReproduction Steps
I tried updating PCSX2 on an old Intel MacBook Air, and it crashed at launch. I bisected the builds, with v1.7.5847 working fine and all builds from v1.7.5849 were broken. (There was no v1.7.5848 release).
Because the crash was instant at launch, there were no logs. However I noticed that if I enable logging as well as the log window (in the previous build), an alert would pop up and I could get a screenshot of the log window.
I tested on a 2015 MacBook Air:
2.2Ghz Core i7
Intel HD 6000
Also tested on a 2015 MacBook Pro with the same results:
2.7 Ghz Core i5
Intel Iris Graphics 6100
(I should also note that they are both running Sonoma via OCLP, though this shouldn't be an issue since v1.7.5847 works fine).
Expected Behavior
No response
PCSX2 Revision
v1.7.5849
Operating System
macOS 14 (Sonoma)
If Linux - Specify Distro
No response
Logs & Dumps
No response
The text was updated successfully, but these errors were encountered: