DOTween call kill when use AwaitForComplete

[821869798]

When I use the extension method AwaitForComplete of DOTween to wait for completion, using the Kill method will cause the await to never be released. The following logs will never be printed,Unitask also seems to have a memory leak.

    void Start()
    {
        Test22();
        Invoke("StopTest", 0.5f);
    }

    async void Test22()
    {
        await Test2();
        Debug.Log("Test2 Complete");
    }

    async UniTask Test2()
    {
        await this.transform.DOMove(Vector3.one, 1f).AwaitForComplete();
        Debug.Log("Move Complete");
    }

    private void StopTest()
    {
        this.transform.DOKill();
    }

[hadashiA]

Since AwaitForComplete explicitly waits for Complete only, is this behavior not inevitable?

We have the following options:

• You can pass a CancellationToken to AwaitForComplete, which can be reliably controlled by canceling with kill.
• If you use await this.transform.DOMove(Vector3.one, 1f);, the UniTask is cleaned up with DOKill.

[821869798]

I use WeakReference to observe that the underlying objects can be released when UniTask Track is disabled.

void Start()
{
    Test1().Forget();
    Invoke("StopTimer", 0.5f);
}

async UniTask Test1()
{
    await Test2();
    Debug.Log("Test2 Complete");
}

WeakReference wr1;
WeakReference wr2;
async UniTask Test2()
{
    var tween = this.transform.DOMove(Vector3.one, 1f);
    wr1 = new WeakReference(tween);
    var task = tween.AwaitForComplete();
    wr2 = new WeakReference(task.source);
    await task;
    Debug.Log("Move Complete");
}

private void StopTimer()
{
    this.transform.DOKill();

    GC.Collect();

    Debug.Log($"live status: {wr1.IsAlive} {wr2.IsAlive}");
}

Regarding the suggestions you provided:

• Using CancellationToken is a bit cumbersome and can introduce GC garbage. It is easier to use DOKill to cancel await.
• I understand that it can be used in that way, but I only need to execute the code after await when the Tween completes normally, not when it is killed.

If possible, I suggest listen for the onKill event in TweenConfiguredSource, and internally call core.TrySetCanceled() to return the TweenConfiguredSource object to the object pool. I have tried it myself and it runs correctly.