-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
net: concurrent map write in DNS resolution #50440
Comments
Does this happen repeatedly? Can you show us code to recreate the problem? Thanks. |
This is odd. The code is clearly using a lock around the map writes. I don't see how this is possible. Unless there is something corrupting memory. |
Yep, I analyzed a simple code, but this is also the doubt。
… 2022年1月5日 下午1:38,Ian Lance Taylor ***@***.***> 写道:
This is odd. The code is clearly using a lock around the map writes. I don't see how this is possible. Unless there is something corrupting memory.
—
Reply to this email directly, view it on GitHub <#50440 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALFKFGI4MTXNRNPAGZADMNDUUPKNJANCNFSM5LJBCK2Q>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Possibly related to #49075? |
Do you have the exact commit causing this ? |
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
Found in the process of github action ci/cd, no recurring method was found
What did you expect to see?
no panic.
What did you see instead?
concurrent fault in singleflight.
The text was updated successfully, but these errors were encountered: