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
runtime: fatal error: timer data corruption #60050
Comments
One more result from greplogs. Failing in approximately the same place: 2023-05-05T19:20:01-f90bb8a/linux-amd64-race |
In triage, we'll wait for more failures. |
Note that you have to add the issue to the Test Flakes project for |
Found new dashboard test flakes for:
2023-04-18 15:42 freebsd-amd64-race go@56c44227 runtime (log)
2023-05-05 19:20 linux-amd64-race go@f90bb8a3 runtime (log)
|
This trybot failure is very likely to be the same root cause: https://storage.googleapis.com/go-build-log/345b5fc2/linux-amd64-race_40fbb72b.log. It's in the same benchmark as the other failures, and it's much more likely the timer.pp got stomped than |
Change https://go.dev/cl/497215 mentions this issue: |
Currently the BenchmarkSetType* benchmarks are racy: they call heapBitsSetType on an allocation that might be in a span in-use for allocation on another P. Because heap bits are bits but are written byte-wise non-atomically (because a P assumes it has total ownership of a span's bits), two threads can race writing the same heap bitmap byte creating incorrect metadata. Fix this by forcing every value we're writing heap bits for into a large object. Large object spans will never be written to concurrently unless they're freed first. Also, while we're here, refactor the benchmarks a bit. Use generics to eliminate the reflect nastiness in gc_test.go, and pass b.ResetTimer down into the test to get slightly more accurate results. Fixes golang#60050. Change-Id: Ib7d6249b321963367c8c8ca88385386c8ae9af1c Reviewed-on: https://go-review.googlesource.com/c/go/+/497215 Reviewed-by: Austin Clements <austin@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> Auto-Submit: Michael Knyszek <mknyszek@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
Existing failure from #55308 (comment): https://build.golang.org/log/83ab44e57523849b0c1ce7a9c63644943c54fbfd
The text was updated successfully, but these errors were encountered: