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
database/sql: data race on rows.releaseConn #9716
Comments
May be related to: |
Is there something I'm missing w.r.t. the line numbers in the race report? They seem completely bogus. E.g:
my line 1957 looks like this: |
Oh, my bad. It was my tree that was completely bogus. Please ignore that. |
It's very strange. goroutine 61 runs |
It looks like another incarnation of a bug fixed upstream by: Just ignore everything below runtime.goexit in stack of goroutine 61. Then it looks pretty consistent. |
so it's time to update the race runtime again? or are you waiting until |
I can't imagine why line 1435 and 1436 make race condition.
|
minux, you may file an issue if you wish |
methane, does not make sense to me either |
Here is another crash in the same place. Starts looking alarming.
http://build.golang.org/log/045696ee3a83e4bc4055222ffc905f1c5e4d8086 |
That suggests that either db.mu is leaked, or there's something terribly wrong with the compiler or runtime. Given the volume of problems lately I'd be inclined to think that the latter is more likely. |
There's a lot of skepticism here and there are no later reports, so assuming this is some kind of corruption that has been fixed. |
Race builder says:
http://build.golang.org/log/bfca7707a0ccb2dd15e8228eb5b97434c33d1143
There is a runtime error after that, but the race still can be true.
The text was updated successfully, but these errors were encountered: