Closed ikolombet closed 2 years ago
Are you using macOS 12? And are you using the race detector? The failure looks like #49138
Try setting environment variable MallocNanoZone=0
.
You're right, this is most likely a duplicate of #49138. I was indeed using the race detector and MallocNanoZone=0
does help. Thanks!
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Was running "go test" for a project I'm working on. After switching to an Apple Silicon Macbook Pro I started experiencing random crashes. Which don't reproduce on an Intel-based Mac I was using previously.
What did you expect to see?
Should not crash.
What did you see instead?
Sometimes the tests crashed, although most of the time they pass. Hard to reproduce. Crashes are different too. Sometimes the "go test" program hanged/deadlocked. I'm not sure if all of this related to the same bug, or maybe these all are different bugs, but I think all of this somehow related to macOS Monterey or arm64 architecture, or a combination of both.
So far I've got:
Crash 1
SIGABRT
withmalloc: Heap corruption detected, free list is damaged at 0x60000125f660
Go stacktrace
Apple crash report
Crash 2
SIGABRT
with"type":"EXC_BAD_ACCESS","signal":"SIGABRT","subtype":"KERN_INVALID_ADDRESS'
Go stacktrace
Apple crash report
Crash 3
Another
Heap corruption detected
, different go stacktraceGo stacktrace
Apple crash report
Crash 4
Another SIGABRT, maybe an interesting/helpful stacktrace? Unfortunately, I don't have an Apple report for this one.
Go stacktrace
Hang up 1
My test suite just hanged with one process consuming 99.9% cpu.
lldb stracktrace
Activity monitor sample process
Hang up 2
Same here, different stacktrace.
lldb stacktrace
I'll see if I can make a repro, although it may take a while, I don't have much experience debugging such things.