Lukasz Dorau

Windows Clang CI job still does not work on windows-2022, but it works in CI on windows-2019, so it is not a high priority bug any more.

Logs attached: [log1.zip](https://github.com/user-attachments/files/21714992/log1.zip) [log2.zip](https://github.com/user-attachments/files/21714993/log2.zip)

The culprit is (found by `git-bisect`): ``` 7930e59d71a3bf21d747c539c310b9825e7ddee0 is the first bad commit commit 7930e59d71a3bf21d747c539c310b9825e7ddee0 Author: Rafal Rudnicki Date: Mon Jul 21 14:26:48 2025 +0000 implement umfPoolTrimMemory --- bisect found...

The last failure: https://github.com/ldorau/unified-memory-framework/actions/runs/16902790459/job/47885775331

5 of 6 weekly CI builds failed because of this issue: https://github.com/oneapi-src/unified-memory-framework/actions/runs/16843892970

Next failure: https://github.com/ldorau/unified-memory-framework/actions/runs/16955859410/job/48057824688

It can be connected with: https://github.com/oneapi-src/unified-memory-framework/issues/1492

Next failure: https://github.com/oneapi-src/unified-memory-framework/actions/runs/16962600184/job/48079262217

> The culprit is (found by `git-bisect`): > > ``` > 7930e59d71a3bf21d747c539c310b9825e7ddee0 is the first bad commit > commit 7930e59d71a3bf21d747c539c310b9825e7ddee0 > Author: Rafal Rudnicki > Date: Mon Jul 21 14:26:48...

This is the real scenario (see also: https://github.com/oneapi-src/unified-memory-framework/pull/1270#issuecomment-2836438295): a) thread **T2** allocates memory region R (for example: `0x100-0x300` - address `0x100` and size `0x200`) and adds it to the tracker...