-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: failure of sweet/fogleman-fauxgl on darwin/amd64 on go1.20 #58533
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
Comments
Reports a data race under the race detector. This may be the underlying issue.
So just a bad benchmark, then?
So, the answer might be no. |
Yeah, that's probably it, it just has races. To be fair, I'm not totally sure this code is super well-maintained these days. We might want to consider just moving away from this benchmark. (Originally we ran it as sort of an interesting math/interface/etc. benchmark, but I'm not sure we ever got any super strong signal from it.) I've been thinking about revamping the Sweet benchmarks a little and replacing a bunch of the benchmarks that don't seem to give us a strong signal one way or the other. We also have quite a few bent benchmarks that I think are noisy in unhelpful ways. I'll open a bug for this cleanup. |
Hm, fixing that race doesn't completely fix the problem. I did this:
Which makes the race detector happy. But the program still crashes in the ways described above. |
I forgot to tag the CLs properly (i.e. I was missing golang/go as a prefix). This benchmark is now gone. |
I think this still may be demonstrating a runtime bug on Darwin. |
That's a good point, I missed that in your last reply. |
The benchmark has been removed from the benchmark suite. To reproduce you now need to checkout I bisected to find the CL that fixed this issue at tip. It was https://go-review.googlesource.com/c/go/+/467015 . Its backport is already in for 1.20.2, so this should be fixed when 1.20.2 comes out. I will leave this issue open and recheck after 1.20.2 is out. |
Thanks Keith! The removal was perhaps a bit premature in that it made it harder to reproduce the issue. Sorry about that. :( |
Ok, this looks fixed in 1.20.2. |
To reproduce:
Crashes in a bunch of random ways, all gc-adjacent. Zombie objects, 0xb01dfacedebac1e errors, driver segfaults, etc. (A few traces pasted below.)
Fails on both 1.20 and 1.20.1. Seems to work fine on both 1.19.4 and tip.
I'm running Ventura 13.0.1 (
Darwin Kernel Version 22.1.0
).Seems to work fine on linux.
Possibly related to #54760 ? Seems somewhat different but the fix there turned this benchmark off on arm64. I wonder if darwin/arm64 fails also, but we need to reenable this benchmark on that platform to check.
@mknyszek @prattmic
The text was updated successfully, but these errors were encountered: