-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Crash when link both vino and tbb or tcmalloc on call ov::core.comile_model
#28551
Comments
Hi @Jsy0220, Please provide a version of TBB you use in your application. It can be case that different versions of TBB (yours and one linked to OpenVINO) can conflict that leads to crash. Best regards, |
@Jsy0220 Could you please compile OpenVINO with configuration |
@wangleis Hi, I tried to compile OpenVINO with configuration -DENABLE_SYSTEM_TBB=ON, but it seems be reseted to OFF by vino. I use cmake configs as following:
when configure done, check by
from which you can see the |
@Jsy0220 Looks like there is no system tbb in your system. May I ask which other tbb version do you use besides OpenVINO? |
@wangleis hi, actually, I don't need tbb in my application directly. So I don't think I use any other tbb, or do you have any method to check it ? Initially, I add tbb libs which offered by OpenVINO by accident and then crash happened, so I want to know why. And someone found if link both vino and tcmalloc also reproduce the same crash, but I haven't tried it. I think it maybe caused by the same reason. I need to use both tcmalloc and vino next. So I want to find the resolution urgently. |
@Jsy0220 Thanks for your clarification. Could you share the following detail system configuration and steps to reproduce the issue?
Another option is using cmake configuration |
@wangleis Platform: linux the steps to reproduce:
I will try the cmake configuration -DTHREADING=OMP, but I prefer tbb instead of openmp for some reasons. |
Hi, sorry for repeating the issue, but no more reply for this Issue
I use vino 2024.5, same problem found in 2024.6.
The text was updated successfully, but these errors were encountered: