If I run the Mac_Runner in the app folder directly, it gives this:
| /Users/daniellurie/Library/Mobile\ Documents/com\~apple\~CloudDocs/Downloads/Pixel\ Composer\ 1.18.002m.app/Contents/MacOS/Mac_Runner ; exit;
(base) daniels-mini-2:~ daniellurie$ /Users/daniellurie/Library/Mobile\ Documents/com\~apple\~CloudDocs/Downloads/Pixel\ Composer\ 1.18.002m.app/Contents/MacOS/Mac_Runner ; exit;
2024-11-18 19:30:17.357 Mac_Runner[55151:1500117] Nil context detected 2 024-11-18 19:30:17.357 Mac_Runner[55151:1500117] Command Line = "/Users/daniellurie/Library/Mobile Documents/com~apple~CloudDocs/Downloads/Pixel Composer 1.18.002m.app/Contents/MacOS/Mac_Runner" 2024-11-18 19:30:17.373 Mac_Runner[55151:1500117] !!!!######## rendersize=(966.000000,620.000000) - displayWidthHeight(966,620) 2024-11-18 19:30:17.411 Mac_Runner[55151:1500117] Data path = </Users/daniellurie/Library/Application Support/com.MakhamDev.PixelComposer> 2024-11-18 19:30:17.412 Mac_Runner[55151:1500117] Reachable = have internet 2024-11-18 19:30:17.412 Mac_Runner[55151:1500117] requested file - /Users/daniellurie/Library/Mobile Documents/com~apple~CloudDocs/Downloads/Pixel Composer 1.18.002m.app/Contents/Resources/game.ios *************************************** * YoYo Games Mac Runner V0.1 * *************************************** CommandLine: -game "/Users/daniellurie/Library/Mobile Documents/com~apple~CloudDocs/Downloads/Pixel Composer 1.18.002m.app/Contents/Resources/game.ios" MemoryManager allocated: 712329 Processing command line -game "/Users/daniellurie/Library/Mobile Documents/com~apple~CloudDocs/Downloads/Pixel Composer 1.18.002m.app/Contents/Resources/game.ios" Segmentation fault: 11 logout Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. |
| A "Segmentation fault: 11" error in the YoYo Games Mac runner typically indicates that your game is attempting to access memory that it is not allowed to, which could be due to a programming error causing the game to try and read or write to a corrupted or invalid memory address, often resulting from a pointer issue or accessing uninitialized variables. Key points about this error: Memory Access Violation: The core issue is that your game code is trying to access memory that is not allocated to it, which is considered a serious error in programming. Potential Causes: Null Pointer Dereferencing: Trying to access a variable that is not pointing to a valid memory location (like using a variable that hasn't been assigned a value properly). Array Out-of-Bounds Access: Accessing an element in an array that is outside of its defined range. Memory Corruption: A previous memory allocation issue might have corrupted the memory space your game is trying to access. Unreleased Memory: Failing to properly deallocate memory that is no longer needed, leading to potential memory conflicts. |