*: support memTracker.detach for HashJoin, Apply and IndexLookUp in Close func (#54095)

[ti-chi-bot]

This is an automated cherry-pick of #54095

What problem does this PR solve?

Issue Number: close #54005

Problem Summary:

What changed and how does it work?

Before:

After:

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.

Fixed the issue of abnormally high memory usage caused by memTracker not being detached in HashJoin and IndexLookUp operators when used as the inner side of the Apply operator.

[XuHuaiyu]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wshwsh12, zanmato1984

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 [wshwsh12,zanmato1984]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-07-11 05:48:34.956785476 +0000 UTC m=+509412.192019584: ☑️ agreed by zanmato1984.
• 2024-07-11 06:19:26.392786894 +0000 UTC m=+511263.628021007: ☑️ agreed by wshwsh12.

[zanmato1984]

/retest

[zanmato1984]

/retest

[zanmato1984]

/retest

[XuHuaiyu]

/retest

[wuhuizuo]

/review please found the possible nil pointer dereference issues.

[ti-chi-bot]

@wuhuizuo:
There are some possible nil pointer dereference issues in this pull request:

• In IndexLookUpExecutor.Close(), the e.memTracker is set to nil without detaching it first. This could cause a panic if the Close() function is called again later.
• In HashJoinExec.Close(), the e.hashJoinCtx.diskTracker is set to nil without detaching it first. This could cause a panic if the Close() function is called again later.
• In NestedLoopApplyExec.fetchAllInners(), the e.innerList is reset without checking if it is nil. This could cause a panic if it is not initialized yet.

In response to this:

/review please found the possible nil pointer dereference issues.

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.