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: SIGSEGV in allocNeedsZero
on darwin
#58715
Comments
Found new dashboard test flakes for:
2023-01-17 01:51 darwin-amd64-11_0 tools@8e949673 go@145dd384 TestGoplsSourceDoesNotCallTokenFileMethods (log)
2023-02-16 18:10 darwin-amd64-12_0 tools@ad4fc28a go@518889b3 x/tools/gopls/internal/regtest/diagnostics.TestIssue37978 (log)
2023-02-16 19:20 darwin-amd64-nocgo tools@e5b99481 go@031401a7 TestLSP (log)
|
The stack trace implies loading a nil |
I want to look into whether this is actually only happening on Darwin. |
I see it once on freebsd in 2021: |
Found new dashboard test flakes for:
2023-04-04 14:19 darwin-amd64-nocgo text@48e4a4a9 go@42f558bd x/text/message/pipeline.TestFullCycle (log)
|
Found new dashboard test flakes for:
2023-05-25 16:41 darwin-amd64-11_0 tools@ed90c6d2 go@789701e9 x/tools/gopls/internal/regtest/diagnostics.TestIssue37978 (log)
2023-06-22 21:46 darwin-amd64-12_0 tools@c8278fe9 go@6dce882b x/tools/go/packages.TestAll (log)
|
Found new dashboard test flakes for:
2023-07-06 20:34 darwin-amd64-12_0 tools@124ebfa4 go@312920c0 x/tools/go/analysis/passes/composite.Test (log)
|
Found new dashboard test flakes for:
2023-10-10 15:06 darwin-amd64-12_0 tools@8954aa7a go@aa8e4c5e x/tools/gopls/internal/regtest/diagnostics.TestIssue37978 (log)
|
Found new dashboard test flakes for:
2023-11-07 21:16 darwin-amd64-12_0 tools@51df92b2 go@9e90a15b x/tools/gopls/internal/regtest/diagnostics.TestIssue37978 (log)
|
Found new dashboard test flakes for:
2023-12-11 23:10 darwin-amd64-nocgo tools@f40889dc go@f4ff0e25 x/tools/go/analysis/passes/deepequalerrors (log)
|
@golang/runtime, is this another symptom of #60449 or do we think it has a separate root cause? |
I believe it's another symptom. I recall investigating this and concluding that it's memory corruption. I double-checked just now and yeah, the failing line doesn't really make sense (that index is write-once, but if it was just allocated and the wrong index was being set up, then we'd be seeing these crashes in a lot more places). |
I added this as a condition to #60449, closing now as a duplicate. |
Found new dashboard test flakes for:
2024-01-22 20:52 darwin-amd64-11_0 tools@e2ca5942 go@a95136a8 x/tools/go/analysis/passes/stdmethods.TestAnalyzeEncodingXML (log)
|
(Pulled out from #55167 (comment).)
The text was updated successfully, but these errors were encountered: