Sporadic kills with `cargo run` on macOS 12

[ehuss]

Problem

Since recently updating to macOS 12.0.1 (Monterey), I have been experiencing sporadic issues with security failures causing the kernel to kill the process before it starts.

In the logs, I see the following messages:

default 11:54:02.325853-0800 kernel ASP: Security policy would not allow process: 33133, /Users/eric/Proj/rust/toml-rs/scratch/a/target/debug/a-337f91948997ff1e
default 11:54:02.325856-0800 kernel ASP: Could not find reference 20142, process must have died

It happens very randomly. Sometimes it will happen constantly, and sometimes it might not happen for several minutes of repeated runs.

I'm not sure what "Could not find reference" means. Is that perhaps the pid of cargo itself?

Steps

Run touch src/main.rs ; cargo run a few times on a smallish project, like something that depends on toml.

Possible Solution(s)

I haven't had a chance to investigate more. This doesn't happen on all projects (I haven't had a problem with building cargo for example). It doesn't seem to matter where I run cargo run from (editor, terminal, etc.).

Notes

No response

Version

cargo 1.58.0-nightly (6c1bc24b8 2021-10-24)
release: 1.58.0
commit-hash: 6c1bc24b8b49d4bc965f67d7037906dc199c72b7
commit-date: 2021-10-24
host: x86_64-apple-darwin
libgit2: 1.3.0 (sys:0.13.23 vendored)
libcurl: 7.77.0 (sys:0.4.49+curl-7.79.1 system ssl:(SecureTransport) LibreSSL/2.8.3)
os: Mac OS 12.0.1 [64-bit]

[weihanglo]

Cannot reproduce it on 12.1 Beta (x86_64). I think it's related to code signing or so, as this article describing.

Could you check the attributes on the binary via xattr <binary>?

[ehuss]

I can't reproduce it now. I'm going to close this, as I don't think anyone else has reported it. I suspect it was just a temporary problem on my machine. I'll investigate more if it happens again.

[arempe93]

Started learning Rust this week and this has been happening the entire time intermittently. Exact symptoms and touch/run repro, except on Big Sur.

Mac OS 11.6.0

ASP: Security policy would not allow process: 46608, /Users/andrew/Documents/src/personal/learn-rust/minigrep/target/debug/deps/minigrep

Running the xattr target/debug/minigrep @weihanglo suggested has no output.

Idk if this is helpful but i tried changing the repro to

rm -rf target; touch src/main.rs; cargo run

Even if the kill gets triggered, you can run the output binary directly ./target/debug/minigrep and it won't get killed.

[ehuss]

Hm, strange, I can go ahead and reopen.

https://developer.apple.com/forums/thread/663456 contains some investigation. I wonder if it is related to the way cargo hard-links the executable just before running it.

[extrawurst]

facing this issue aswell, happens very randomly

[e9510cba]

+1, i see something like this

    Finished dev [unoptimized + debuginfo] target(s) in 0.64s
     Running `target/debug/name`
[1]    45741 killed     cargo r

cargo 1.56.0 (4ed5d137b 2021-10-04)
rustc 1.56.1 (59eed8a2a 2021-11-01)

Also interesting to note, I'm not on MacOS 12, only MacOS 11.5.2

[charlesroussel]

I have the sameerror. I also got a log trace of when the issue happen.

kernel: (AppleMobileFileIntegrity) AMFI: '<user>/perso/Aoc/target/debug/advent' has no CMS blob?
kernel: (AppleMobileFileIntegrity) AMFI: '<user>/perso/Aoc/target/debug/advent': Unrecoverable CT signature issue, bailing out.
kernel: (AppleMobileFileIntegrity) AMFI: code signature validation failed.
syspolicyd: [com.apple.syspolicy.exec:default] Unable (errno: 2) to read file at <private> for process path: <private> library path: (null)
syspolicyd: [com.apple.syspolicy.exec:default] Terminating process due to Gatekeeper rejection: 45603, <private>
kernel: build_userspace_exit_reason: illegal flags passed from userspace (some masked off) 0x141, ns: 9, code 0x8
kernel: (AppleSystemPolicy) ASP: Sleep interrupted, signal 0x100
kernel: (AppleSystemPolicy) ASP: Security policy would not allow process: 45603, <user>/perso/Aoc/target/debug/deps/advent

Cargo version:

cargo --version
cargo 1.56.0 (4ed5d137b 2021-10-04)

Mac os version: Big Sur 11.5.2

[charlesroussel]

Signature using codesign codesign -dv --verbose=1 target/debug/advent
On a compiled binary:

Executable=<user>/perso/Aoc/target/debug/advent
Identifier=advent-c9a39a776f9fca9d
Format=Mach-O thin (arm64)
CodeDirectory v=20400 size=165168 flags=0x20002(adhoc,linker-signed) hashes=5158+0 location=embedded
Signature=adhoc
Info.plist=not bound
TeamIdentifier=not set
Sealed Resources=none
Internal requirements=none

[hkratz]

@charlesroussel The output looks fine. If you try to run it again, does it work? So far it looked more like a timing issue.