Skip to content
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

goleak executor.(*AnalyzeColumnsExecV2).subMergeWorker #41511

Closed
Tracked by #41316
hawkingrei opened this issue Feb 16, 2023 · 4 comments
Closed
Tracked by #41316

goleak executor.(*AnalyzeColumnsExecV2).subMergeWorker #41511

hawkingrei opened this issue Feb 16, 2023 · 4 comments
Assignees
Labels
affects-7.0 component/test may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 may-affects-6.5 may-affects-6.6 severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@hawkingrei
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

2. What did you expect to see? (Required)

3. What did you see instead (Required)

--- PASS: TestGlobalMemoryControlForAnalyze (3.22s)

PASS

coverage: 15.6% of statements

goleak: Errors on successful test run: found unexpected goroutines:

[Goroutine 43419 in state sleep, with time.Sleep on top of the stack:

goroutine 43419 [sleep]:

time.Sleep(0x5f5e100)

	GOROOT/src/runtime/time.go:195 +0x135

github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).subMergeWorker(0xc007da2330, 0xc0068bdf80, 0xc006712000, 0x2, 0x0)

	executor/analyze_col_v2.go:602 +0x1e5

created by github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).buildSamplingStats

	executor/analyze_col_v2.go:260 +0x685


 Goroutine 43421 in state sleep, with time.Sleep on top of the stack:

goroutine 43421 [sleep]:

time.Sleep(0x5f5e100)

	GOROOT/src/runtime/time.go:195 +0x135

github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).subMergeWorker(0xc007da2330, 0xc0068bdf80, 0xc006712000, 0x2, 0x2)

	executor/analyze_col_v2.go:602 +0x1e5

created by github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).buildSamplingStats

	executor/analyze_col_v2.go:260 +0x685


 Goroutine 43422 in state sleep, with time.Sleep on top of the stack:

goroutine 43422 [sleep]:

time.Sleep(0x5f5e100)

	GOROOT/src/runtime/time.go:195 +0x135

github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).subMergeWorker(0xc007da2330, 0xc0068bdf80, 0xc006712000, 0x2, 0x3)

	executor/analyze_col_v2.go:602 +0x1e5

created by github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).buildSamplingStats

	executor/analyze_col_v2.go:260 +0x685


 Goroutine 43420 in state sleep, with time.Sleep on top of the stack:

goroutine 43420 [sleep]:

time.Sleep(0x5f5e100)

	GOROOT/src/runtime/time.go:195 +0x135

github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).subMergeWorker(0xc007da2330, 0xc0068bdf80, 0xc006712000, 0x2, 0x1)

	executor/analyze_col_v2.go:602 +0x1e5

created by github.com/pingcap/tidb/executor.(*AnalyzeColumnsExecV2).buildSamplingStats

	executor/analyze_col_v2.go:260 +0x685

]

--

Coverage runner: Not collecting coverage for failed test.

The following commands failed with status 1

/home/jenkins/.tidb/tmp/63a9840cd0739f2c243bb46478607469/sandbox/linux-sandbox/7481/execroot/__main__/bazel-out/k8-fastbuild/bin/executor/analyzetest/analyzetest_test_/analyzetest_test.runfiles/__main__/executor/analyzetest/analyzetest_test_/analyzetest_test

4. What is your TiDB version? (Required)

@hawkingrei hawkingrei added the type/bug The issue is confirmed as a bug. label Feb 16, 2023
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 may-affects-6.5 may-affects-6.6 labels Feb 16, 2023
@aytrack
Copy link
Contributor

aytrack commented Feb 17, 2023

since it's a ut leak, downgrade severity to major

@chrysan chrysan self-assigned this Feb 17, 2023
@hawkingrei
Copy link
Member Author

I have see it again for a long time. If we find it again. we will reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.0 component/test may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 may-affects-6.5 may-affects-6.6 severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

5 participants