Game crashes on launch - Apple M1 Mac Monterey

[0xhjx3]

Game crashes immediately when trying to launch on Apple M1 Mac, OS 12.0.1 Monterey. will appreciate any help :)

 
Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

VM Region Info: 0 is not in any region.  Bytes before following region: 4368089088
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      1045bc000-104a6d000    [ 4804K] r-x/rwx SM=COW  ...MacOS/Celeste

Application Specific Information:
dyld4 config: DYLD_INSERT_LIBRARIES=/Users/USER/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steamloader.dylib:/Users/USER/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/gameoverlayrenderer.dylib
abort() called

Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage

[eykanal]

+1. Same error after update to Mac 12.0.1.

[rhobit]

me too :(

[MoreTacos]

Same issue here. Stopped working after update.

[Frank]

same here on:
```
Model: MacBookPro16,1, BootROM 1715.40.15.0.0 (iBridge: 19.16.10548.0.0,0), 8 processors, 8-Core Intel Core i9, 2.3 GHz, 32 GB, SMC
Graphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In
Display: Color LCD, 3072 x 1920 Retina, Main, MirrorOff, Online
Graphics: AMD Radeon Pro 5500M, AMD Radeon Pro 5500M, PCIe, 4 GB
Memory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, Micron, MT40A2G8NEA-062E:J
Memory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, Micron, MT40A2G8NEA-062E:J
```

main thread traceback:
```
Thread 0 Crashed:: MainThrd Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x7ff81506c112 __pthread_kill + 10
1 libsystem_pthread.dylib 0x7ff8150a2233 pthread_kill + 263
2 libsystem_c.dylib 0x7ff814feed10 abort + 123
3 Celeste 0x10027117e mono_post_native_crash_handler + 14
4 Celeste 0x1002646fb mono_handle_native_crash + 475
5 Celeste 0x1001e16fe altstack_handle_and_restore + 206
6 libsystem_platform.dylib 0x7ff8150b50f0 _platform_strcmp + 80
7 libFNA3D.0.dylib 0x1060b2c26 OPENGL_PrepareWindowAttributes + 422
8 libFNA3D.0.dylib 0x1060a95ec FNA3D_PrepareWindowAttributes + 124
9 ??? 0x10973a5c8 ???
10 ??? 0x105dc444b ???
11 ??? 0x10089b3bb ???
12 ??? 0x10089b7e1 ???
13 Celeste 0x10027b2f0 mono_jit_runtime_invoke + 1568
14 Celeste 0x1003aef67 mono_runtime_invoke_checked + 135
15 Celeste 0x1003b64c6 mono_runtime_exec_main_checked + 118
16 Celeste 0x1001d770d mono_jit_exec + 381
17 Celeste 0x1001da836 mono_main + 8646
18 Celeste 0x10018fc31 main + 993
19 dyld 0x1106b74fe start + 462
```

sounds like an opengl issue

[ericlovesmath]

Same here, unfortunate. If anyone has a temporarily solution until when/if a patch comes, that would be great.

[UnlikePaladin]

Still an issue, and apparently the developer who ported the game doesn't have access to a macOS Monterey (nothing newer than Mojave) and they don't want to work on macOS ports anymore so let's just pray there's a fix or patch at some point either from Apple to rectify what they broke or from the Celeste macOS porter/developer. It's also worth noting this is an issue on both Intel and Apple Sillicon Macs, Monterey broke a bunch of OpenGL related stuff like VSYNC so yeah. :/
EDIT: Peeked and looked at the game files, Celeste appears to be mono based like Stardew Valley but Stardew works fine so a mono update might fix it, so it might not be as complicated to fix, also the game files contain MoltenVK which enables Vulkan rendering on top of Metal so worst case scenario OpenGL is ripped out and replaced with it by default
Article Link[appleinsider.com]

[ryanhcode]

Having this issue aswell from a MacBook Air running Monterey. Anybody find any solutions/workarounds?

[UnlikePaladin]

Originally posted by ryanhcode:

Having this issue aswell from a MacBook Air running Monterey. Anybody find any solutions/workarounds?

I've found one, opting into the old 1.2.5 Beta which says outdated works, it's obviously not the latest version but at least this way you can actually play the game.
EDIT: tried 1.3.2 it also works

[Zedeff]

Ive found mine seems to work fine until I plug a controller in. Then it instantly crashes

[eykanal]

Same here, pretty much same trace as #4 above. Both on 12.0.1 and on newly updated 12.1.

[Frank]

Are the developers even maintaining this game anymore???

[TheOnlyMrCat]

Perhaps an important note is that installing the Everest mod loader (tested: version 3614 installed through Olympus) fixes this crash on launch, however, creates a new issue with FMOD.

After installing Everest, even if the files are validated through steam to remove it, the game opens a window and starts the title sequence, eventually crashing when it tries to load the audio engine. It fails with ERR_HEADER_MISMATCH, which from what I can tell, means the bundled FMOD library version is not the same as the version the game was compiled against. I cannot determine whether this is an issue with Celeste itself or with Everest.

[ericlovesmath]

Originally posted by TheOnlyMrCat:

Perhaps an important note is that installing the Everest mod loader (tested: version 3614 installed through Olympus) fixes this crash on launch, however, creates a new issue with FMOD.

After installing Everest, even if the files are validated through steam to remove it, the game opens a window and starts the title sequence, eventually crashing when it tries to load the audio engine. It fails with ERR_HEADER_MISMATCH, which from what I can tell, means the bundled FMOD library version is not the same as the version the game was compiled against. I cannot determine whether this is an issue with Celeste itself or with Everest.

Thank you so much! This worked perfectly for me

[TheOnlyMrCat]

Ah! I now see the fmod issue was unrelated; I had another version of fmod installed separately.

That means the solution works: installing the Everest modding API will stop this crash from occurring. You can also uninstall it, if you don't want it, by using the normal steam "Verify integrity of game files" option, and even after uninstalling Everest, the game will no longer crash.

[finscn]

macOS 12 can't run this game

My mac :
MacBook Pro (13-inch, 2020, Four Thunderbolt 3 ports)

CPU: 2.3 GHz Intel Core i7
RAM: 32 GB 3733 MHz LPDDR4X
GPU: Intel Iris Plus Graphics 1536 MB

-------

When I try to run Celeste , It's crashed and closed.
Then there is an error dialog of macOS.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: Celeste [1668]
Path: /Users/USER/Library/Application Support/Steam/*/Celeste.app/Contents/MacOS/Celeste
Identifier: com.celeste
Version: 1.0 (1.2.3.2)
Code Type: X86-64 (Native)
Parent Process: steam_osx [799]
Responsible: steam_osx [799]
User ID: 501

Date/Time: 2022-01-06 04:25:20.5669 +0800
OS Version: macOS 12.1 (21C52)
Report Version: 12
Bridge OS Version: 6.1 (19P647)
Anonymous UUID: A53D9BA4-AB01-2193-956A-E7028A851273

Sleep/Wake UUID: 0A257BF5-C176-40D8-9179-24563A5D1F2D

Time Awake Since Boot: 4000 seconds
Time Since Wake: 805 seconds

System Integrity Protection: disabled

Crashed Thread: 0 MainThrd Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

VM Region Info: 0 is not in any region. Bytes before following region: 4383502336
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 10546f000-105920000 [ 4804K] r-x/rwx SM=COW ...MacOS/Celeste

Application Specific Information:
dyld4 config: DYLD_INSERT_LIBRARIES=/Users/rocky/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steamloader.dylib:/Users/rocky/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/gameoverlayrenderer.dylib
abort() called


Thread 0 Crashed:: MainThrd Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x7ff81d38e112 __pthread_kill + 10
1 libsystem_pthread.dylib 0x7ff81d3c4214 pthread_kill + 263
2 libsystem_c.dylib 0x7ff81d310d10 abort + 123
3 Celeste 0x10555317e mono_post_native_crash_handler + 14
4 Celeste 0x1055466fb mono_handle_native_crash + 475
5 Celeste 0x1054c36fe altstack_handle_and_restore + 206
6 libsystem_platform.dylib 0x7ff81d3d70f0 _platform_strcmp + 80
7 libFNA3D.0.dylib 0x10b466c26 OPENGL_PrepareWindowAttributes + 422
8 libFNA3D.0.dylib 0x10b45d5ec FNA3D_PrepareWindowAttributes + 124
9 ??? 0x10b33ad58 ???
10 ??? 0x10ace38bb ???
11 ??? 0x108a183bb ???
12 ??? 0x108a187e1 ???
13 Celeste 0x10555d2f0 mono_jit_runtime_invoke + 1568
14 Celeste 0x105690f67 mono_runtime_invoke_checked + 135
15 Celeste 0x1056984c6 mono_runtime_exec_main_checked + 118
16 Celeste 0x1054b970d mono_jit_exec + 381
17 Celeste 0x1054bc836 mono_main + 8646
18 Celeste 0x105471c31 main + 993
19 dyld 0x10942d4fe start + 462


Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00000001094a8600 rcx: 0x00007ff7baa8f538 rdx: 0x0000000000000000
rdi: 0x0000000000000103 rsi: 0x0000000000000006 rbp: 0x00007ff7baa8f560 rsp: 0x00007ff7baa8f538
r8: 0x00007ff7baa8ef08 r9: 0x00000001057f93d8 r10: 0x0000000000000000 r11: 0x0000000000000246
r12: 0x0000000000000103 r13: 0x00007fc140705850 r14: 0x0000000000000006 r15: 0x0000000000000016
rip: 0x00007ff81d38e112 rfl: 0x0000000000000246 cr2: 0x00000001089ad600