Skip to content

[UR][L0] Move async pool cleanup after queue sync #18331

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 6, 2025

Conversation

kswiecicki
Copy link
Contributor

In a scenario where the AsyncPool freelist contains an entry tied to a free event that hasn't completed yet, performing freelist cleanup before queue sync can result in freeing memory that's actively in use.

@kswiecicki kswiecicki requested a review from a team as a code owner May 6, 2025 11:50
In a scenario where the AsyncPool freelist contains an entry tied to a
free event that hasn't completed yet, performing freelist cleanup before
queue sync can result in freeing memory that's actively in use.
@kswiecicki
Copy link
Contributor Author

kswiecicki commented May 6, 2025

The one failing SYCL e2e test, also fails on the CI jobs from other PRs, eg. https://github.com/intel/llvm/actions/runs/14858136399/job/41717560338 and https://github.com/intel/llvm/actions/runs/14857464574/job/41715519649

# .---command stderr------------
# | /__w/llvm/llvm/llvm/sycl/test-e2e/ThreadSanitizer/check_usm.cpp:28:12: error: CHECK: expected string not found in input
# |  // CHECK: WARNING: DeviceSanitizer: data race

@kswiecicki kswiecicki requested a review from igchor May 6, 2025 12:36
@pbalcer
Copy link
Contributor

pbalcer commented May 6, 2025

@intel/llvm-gatekeepers please merge. The failure is unrelated (#18331 (comment)).

@sarnex sarnex merged commit c9cba79 into intel:sycl May 6, 2025
31 of 32 checks passed
KornevNikita pushed a commit that referenced this pull request May 27, 2025
In a scenario where the AsyncPool freelist contains an entry tied to a
free event that hasn't completed yet, performing freelist cleanup before
queue sync can result in freeing memory that's actively in use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants