runtime: SIGABRT during IP lookup on macOS 11.0 Beta (20A5374g) #41572
Comments
|
Attempting to reproduce this issue with single HTTP requests or multiple goroutines with same/separate HTTP clients has not been fruitful, so the issue seems to be more intricate than just making DNS lookups. The issue does reproduce every time in our code base though, so if there are steps we can take to produce better debug output, let us know. I added the full trace to make sure nothing is missing in the OP. |
|
This looks like the C function Can you run the program under a C debugger and try to figure out what |
ianlancetaylor
added
the
NeedsInvestigation
|
Just adding info in case it helps. I'm on Beta 8 of 11.0 and it gave me the same runtime error while trying to resolve "localhost". Switched to "127.0.0.1" and error went away |
|
Is this still an issue now that macOS 11 is out of beta? |
aclements
added
the
WaitingForInfo
|
I have not seen this issue again in stable Big Sur. |
|
Thanks for following up. I'll close the issue in that case. |
|
This seems to be an issue again for the macos Monterey beta, the error/stracktrace seems to be the same as @blixt originally provided. |
|
This seems to be an issue again for the macos Monterey release. |
|
Can confirm. This is happening with Go 1.17.2, on Mac OS X 12.0.1 on a M1 Pro SoC. |
|
Does the issue still happen with MacOS Monterey if you set the environment variable MallocNanoZone=0? There's a known issue with -race on MacOS 12 (#49138). |
|
I also had this issue when the code is compiled with |
thanks! Switching to localhost helps in my case :) macOS Monterey 12.1 |
chore: "go mod tidy" updates tests (Server): add a reasonable level of unit tests defect (Server): protect against listener data races docs: Add some more godocs refactor (Server/configOptions): update WithDisablePanicRecovery Passing true for this option is redundant. chore (SIDBytes): remove commented code defect: trying to resolve: golang/go#41572 refactor: stop exporting newMessage(...) refactor (Mux): remove Routes() method refactor: prevent data races when writing responses refactor (route): use the Op() receiver method
chore: "go mod tidy" updates tests (Server): add a reasonable level of unit tests defect (Server): protect against listener data races docs: Add some more godocs refactor (Server/configOptions): update WithDisablePanicRecovery Passing true for this option is redundant. chore (SIDBytes): remove commented code defect: trying to resolve: golang/go#41572 refactor: stop exporting newMessage(...) refactor (Mux): remove Routes() method refactor: prevent data races when writing responses refactor (route): use the Op() receiver method
I recently upgraded to Monterey and began seeing this problem, and I can confirm that setting this variable fixed the issue for me. |
Thanks! I was facing similar issue and setting the environment variable MallocNanoZone=0 fixed it for me. |
|
facing the same problem here, after upgrade macos to macOS Monterrey 12.3.1
|
- golang/go#41572 - need to export MallocNanoZone=0 as well [#181129167](https://www.pivotaltracker.com/story/show/181129167) Co-authored-by: Kyle Ong <[email protected]> Co-authored-by: Colin Shield <[email protected]>
- golang/go#41572 - need to export MallocNanoZone=0 as well [#181129167](https://www.pivotaltracker.com/story/show/181129167) Co-authored-by: Kyle Ong <[email protected]> Co-authored-by: Colin Shield <[email protected]>
- golang/go#41572 - need to export MallocNanoZone=0 as well [#181129167](https://www.pivotaltracker.com/story/show/181129167) Co-authored-by: Kyle Ong <[email protected]> Co-authored-by: Colin Shield <[email protected]>
switchboard: Fail fast when CA is invalid switchboard: Remove -race from build command - golang/go#41572 - need to export MallocNanoZone=0 as well [#181630145](https://www.pivotaltracker.com/story/show/181630145) [#181129167](https://www.pivotaltracker.com/story/show/181129167) Co-authored-by: Kyle Ong <[email protected]> Co-authored-by: Ryan Wittrup <[email protected]> Co-authored-by: Colin Shield <[email protected]>
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 envOutputWhat did you do?
The code is performing an HTTPS request using the standard HTTP library and immediately crashes with
SIGABRT.What did you expect to see?
Executable runs successfully.
What did you see instead?
Expand section below to see the full output.
Full session / trace output
The text was updated successfully, but these errors were encountered: