-
Notifications
You must be signed in to change notification settings - Fork 787
Module leak #8153
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
Module leak #8153
Conversation
Currently, ZE_DEBG=4 test shows memory leak. The reason is that we missed the zeModuleDestroy() call when a program build failed. Signed-off-by: Byoungro So <byoungro.so@intel.com>
Signed-off-by: Byoungro So <byoungro.so@intel.com>
@bso-intel, please, merge |
@againull |
Program->State = _pi_program::Invalid; | ||
Result = mapError(ZeResult); | ||
if (Program->ZeBuildLog) { | ||
ZE_CALL_NOCHECK(zeModuleBuildLogDestroy, (Program->ZeBuildLog)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bso-intel, @againull : this change causes a regression that build-log is destroyed before SYCL RT reads it (to report to the user). Please revert (or re-work) the patch
When it is failed to build a program, L0 throws an exception, which causes sycl::program to fail to create.
Because of this, RT won't call piProgramRelease(), which leads to memory leaks.
The solution is to release ZeModule created by plugin when the program build is failed.