forked from intel/llvm
-
Notifications
You must be signed in to change notification settings - Fork 4
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
L0 Memory Leak on Windows in test-e2e\Graph\Explicit\reduction.cpp #267
Labels
Comments
EwanC
added
bug
Something isn't working
Graph Implementation
Related to DPC++ implementation and testing
labels
Jul 18, 2023
EwanC
added a commit
that referenced
this issue
Jul 18, 2023
Cherry-pick commit intel@b78844b from `sycl-graph-patch-4` back to `sycl-graph-develop` until these Windows fails are investigated and resolved * #267 * #268 * #269
EwanC
added a commit
that referenced
this issue
Jul 19, 2023
Cherry-pick commit intel@b78844b from `sycl-graph-patch-4` back to `sycl-graph-develop` until these Windows fails are investigated and resolved * #267 * #268 * #269
If I modify the reduction test to remove the graphs code I still see the memory-leak. Looking at existing e2e reduction tests I think this is a known issue unrelated to our extension intel#9764 |
EwanC
added a commit
that referenced
this issue
Jul 19, 2023
Level Zero memory leaks with reductions are a known issue intel#9764 Only run the leak component of the reduction test on Linux to avoid this issue. Closes #267
Bensuo
pushed a commit
that referenced
this issue
Jul 24, 2023
Level Zero memory leaks with reductions are a known issue intel#9764 Only run the leak component of the reduction test on Linux to avoid this issue. Closes #267
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When run on Windows with the ZE_DEBUG=4 environment variable set, the
test-e2e\Graph\Explicit\reduction.cpp
test reports a memory leak of L0 resources, causing it to failThis leak should be investigated and fixed
The text was updated successfully, but these errors were encountered: