-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal error: acquireSudog: found s.elem != nil in cache #48188
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
This may be tough to solve without a reproduction case. |
getting the same issue.. !!! |
@ianlancetaylor @AdamKorcz Did you find any solutions to prevent this from happening? |
@kuabhish @vignesh-codes Do either of you have a reproducer you can share? |
@prattmic We removed and it worked somehow. I have given a pseudocode of the function here which caused the issue. No more crashes in our service
I am not exactly sure why this issue was happening. We made use of redis pipe for optimisation here. Our production service has lots of traffic per minute. I hope it can help you debug the issue. |
Appending to a global variable without synchronization is a data race. Have you tried running with the race detector? |
hmmm yeah might be coz of that.. have nt checked with race detector. I did not add mutex there since there were no read happening concurrently and was just appending |
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.) |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Reproducer is not yet created.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I encountered this bug after running a go-fuzz fuzzer for about 1 week. The fuzzer is currently not publicly available.
What did you expect to see?
I expected not to see this crash.
What did you see instead?
The text was updated successfully, but these errors were encountered: