util: Resolve RuntimeStatsColl potential unlock mutex

[yibin87]

What problem does this PR solve?

Issue Number: close #55042

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.
    Just a mutex lock changes, using defer to protect it.

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 the issue that queries may get stuck when they are being killed due to exceeding tidb_mem_quota_query.

[tiprow]

Hi @yibin87. 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.

[yibin87]

/cc @wshwsh12 @guo-shaoge

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.8757%. Comparing base (68b529e) to head (f999c64).
Report is 196 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55118        +/-   ##
================================================
+ Coverage   72.7939%   74.8757%   +2.0818%     
================================================
  Files          1562       1566         +4     
  Lines        439174     440961      +1787     
================================================
+ Hits         319692     330173     +10481     
+ Misses        99754      90673      -9081     
- Partials      19728      20115       +387     

Flag	Coverage Δ
integration	49.8786% <100.0000%> (?)
unit	71.8612% <100.0000%> (+0.0746%)	⬆️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	52.5555% <ø> (+6.6789%)	⬆️

[hawkingrei]

replace sync.Metux with syncutil.Mutex which can find the potential mutex in the CI.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-01 05:35:59.02657947 +0000 UTC m=+420475.306627537: ☑️ agreed by hawkingrei.
• 2024-08-01 06:28:42.776163711 +0000 UTC m=+423639.056211780: ☑️ agreed by wshwsh12.

[yibin87]

/test unit-test

[tiprow]

@yibin87: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: guo-shaoge, hawkingrei, wshwsh12

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [guo-shaoge,hawkingrei,wshwsh12]

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

[yibin87]

/retest

[tiprow]

@yibin87: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #55148.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #55646.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #55647.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #55648.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #55649.