-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Goroutine leak when hashJoin triggered spill and sql failed. #50841
Labels
affects-6.5
affects-6.6
affects-7.0
affects-7.1
affects-7.2
affects-7.3
affects-7.4
affects-7.5
affects-7.6
report/customer
Customers have encountered this bug.
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Comments
13 tasks
ti-chi-bot
bot
added
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
labels
Jan 31, 2024
wshwsh12
removed
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
labels
Jan 31, 2024
13 tasks
This was referenced Feb 20, 2024
/found customer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-6.6
affects-7.0
affects-7.1
affects-7.2
affects-7.3
affects-7.4
affects-7.5
affects-7.6
report/customer
Customers have encountered this bug.
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
kill tidb xxxxxxxxxx
2. What did you expect to see? (Required)
No goroutine leak.
3. What did you see instead (Required)
We can see the log, the close process interrupted, I debug and find hashRowContainer's byteConsume is negative and panic in c.memTracker.Detach(). So the hashJoin's children can't call Close() function and cause leak.
4. What is your TiDB version? (Required)
master, v7.5, v7.1,v6.5
The text was updated successfully, but these errors were encountered: