-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
raylib-lua is slow on Apple M1 #5
Comments
Exit code 137 is out of memory error, not sure why/where it happens. I don't have a Mac, so it's tricky to test, I should try with a vm. |
👋🏼 @GarrettAlbright |
I'm afraid I haven't. I haven't had another look at this since I posted this issue. |
I've submitted a pull request for the issue, but one thing I am noticing is performance is not great. Here is a benchmark I've run 100,000 bunnies, 144 FPS max. M1 Mac Mini - 16GB RAM - macOS Ventura 13.4.1
I am not sure why LuaJIT is having these performance issues as I ran raylib_e with a zipfile to make a binary. The branch checkout is from 6 months ago so its a recent code base for LuaJIT. Even ran with |
I think this issue is due to LuaJIT on Mac OS not using JIT for some reason. |
jit = require "jit" print("jit status", jit.status())
|
I'm on a MacBook Air (M1, 2020) running macOS 12.4.
After cloning the repo and subrepos and running
make
, trying to run any of the raylua_* binaries results in:(…or raylua_s or raylua_r) and an exit code of 137.
Searching for "zsh: killed" seems to mostly result in pages relating to running Homebrew or tools installed with it on M1 Macs. I don't think this is Homebrew-related since I'm a boomer who uses MacPorts (if it ain't broke…). Nonetheless I wonder if the issue might still be related to the relatively new M1 hardware and I wonder if anyone else is seeing this issue happen on M1 Macs, or alternatley is running it successfully.
Unfortunately I no longer have easy access to Intel-based Mac hardware to see if the issue is happening there too.
The text was updated successfully, but these errors were encountered: