-
Notifications
You must be signed in to change notification settings - Fork 30.7k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Mac M1/Monterey SIGKILL with exit code 137 (Code Signature Invalid) #40827
Comments
Thanks for reporting, could you provide a minimal repro to the issue? |
I'm getting the same behaviour when importing a native add-on I'm building with Rust (neon). The first time I compile the add-on and run it, it works. However if I recompile after changing anything (e.g. the contents of a string literal) and try to If I restart my machine after recompiling, it works fine. However this means I need to restart every time I make changes, which isn't ideal. I have tried on both I'm also running on ARM MacOS 12.1 This is the crash report:
|
Turns out code signatures are a strict requirement for running ARM binaries on M1 Macs. I resolved my issue by signing the Rust binary with an ad-hoc signature with Given @lukas2's issue is also to do with code signatures on an M1 Mac, I'd say it's fairly likely the same issue and as such probably not related to Node. |
In OpenBoardView/OpenBoardView#239 (comment) i had to add
Mentioning it here since this issue is on the top of search results for |
I am getting this issue when starting Eclipse IDE on mac m1. Yesterday it was working suddenly it is giving me this error. Can any help what will be the issue. Translated Report (Full Report Below)Incident Identifier: 21518B23-4B76-43E2-B75F-908B5838FAC2 Date/Time: 2023-01-31 14:43:43.9396 +0530 Exception Type: EXC_CRASH (SIGKILL (Code Signature Invalid)) Triggered by Thread: 0 Thread 0 Crashed: Thread 0 crashed with ARM Thread State (64-bit): Binary Images: Error Formulating Crash Report: EOF Full Report{"app_name":"eclipse","timestamp":"2023-01-31 14:43:43.00 +0530","app_version":"4.24.0","slice_uuid":"bf0baa93-fe7a-3039-ac22-e0007dc821f4","build_version":"4.24.0.I20220607-0700","platform":0,"bundleID":"org.eclipse.platform.ide","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.1 (22C65)","roots_installed":0,"name":"eclipse","incident_id":"21518B23-4B76-43E2-B75F-908B5838FAC2"} }
], ] Model: MacBookAir10,1, BootROM 8419.60.44, proc 8:4:4 processors, 8 GB, SMC |
I'll convert this to a discussion since it's not strictly speaking a node bug. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Version
v16.13.0
Platform
21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:24 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T8101 arm64
Subsystem
No response
What steps will reproduce the bug?
I Run typescript tests in CLion. It sometimes, not always, crashes with
Afterwards it sometimes randomly works again, most often I have to restart the computer to continue work.
How often does it reproduce? Is there a required condition?
Sometimes
What is the expected behavior?
No Crash
What do you see instead?
No Crash
Additional information
I see this in the log console when it happens:
Interestingly I also sometimes get
pointer authentication failure
, which seems unrelated..The text was updated successfully, but these errors were encountered: