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
severity/major
sig/execution
SIG execution
type/bug
This issue is 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: