analyze table return "analyze worker panic"

[An0nymous0]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

analyze table metabase.metabase_field

Detailed file and table structure: https://asktug.com/t/topic/95448

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

analyze table metabase.metabase_field return analyze worker panic

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

Release Version: v5.1.0
Edition: Community
Git Commit Hash: 8acd5c88471cb7b4d4c4a8ed73b4d53d6833f13e
Git Branch: heads/refs/tags/v5.1.0
UTC Build Time: 2021-06-24 07:10:32
GoVersion: go1.16.4
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false

[lcwangchao]

The some problem with stack:

[2021/07/26 23:01:18.995 +08:00] [ERROR] [analyze.go:1169] ["analyze worker panicked"] [stack="goroutine 59879 [running]:\ngithub.com/pingcap/tidb/executor.(*AnalyzeColumnsExec).subMergeWorker.func1(0x1401e5b2360, 0x1401e5b23c0, 0x1400c3fa480, 0x1)\n\t/Users/wangchao/Code/pingcap/tidb/executor/analyze.go:1167 +0xd0\npanic(0x1025c15a0, 0x104320f70)\n\t/usr/local/go/src/runtime/panic.go:965 +0x14c\ngithub.com/pingcap/tidb/statistics.(*RowSampleCollector).FromProto(0x140050e7f18, 0x0)\n\t/Users/wangchao/Code/pingcap/tidb/statistics/row_sampler.go:242 +0x28\ngithub.com/pingcap/tidb/executor.(*AnalyzeColumnsExec).subMergeWorker(0x1400c3fa480, 0x1401e5b2360, 0x1401e5b23c0, 0x174, 0x140050e7601)\n\t/Users/wangchao/Code/pingcap/tidb/executor/analyze.go:1213 +0x3c0\ncreated by github.com/pingcap/tidb/executor.(*AnalyzeColumnsExec).buildSamplingStats\n\t/Users/wangchao/Code/pingcap/tidb/executor/analyze.go:848 +0x514\n"]

[winoros]

fixed by #25311
will be released in v5.1.1

[ti-srebot]

Please edit this comment or add a new comment to complete the following information

Not a bug

1. Remove the 'type/bug' label
2. Add notes to indicate why it is not a bug

Duplicate bug

1. Add the 'type/duplicate' label
2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

6. Fixed versions