executor: fix hang in hash agg when exceeding memory limit leads to panic

[xzhangxian1008]

What problem does this PR solve?

Issue Number: close #57546

Problem Summary:

What changed and how does it work?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

fix issue that tidb may hang in hash agg when exceeding memory limit leads to panic

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xhebox for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tiprow]

Hi @xzhangxian1008. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[xzhangxian1008]

/cc @wshwsh12 @XuHuaiyu

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.4184%. Comparing base (14ff938) to head (76ed9c0).
Report is 2 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57641        +/-   ##
================================================
+ Coverage   72.8292%   73.4184%   +0.5891%     
================================================
  Files          1676       1676                
  Lines        463753     463802        +49     
================================================
+ Hits         337748     340516      +2768     
+ Misses       105139     102530      -2609     
+ Partials      20866      20756       -110     

Flag	Coverage Δ
integration	43.4379% <58.3333%> (?)
unit	72.2172% <100.0000%> (-0.0072%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.7673% <ø> (ø)
parser	∅ <ø> (∅)
br	45.4468% <ø> (+0.0090%)	⬆️

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[ti-chi-bot]

@xzhangxian1008: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-integration-ddl-test	76ed9c0	link	true	/test pull-integration-ddl-test
idc-jenkins-ci-tidb/check_dev_2	76ed9c0	link	true	/test check-dev2

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.