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
cv::aruco::detectMarkers crashes on AMD processors. #2736
Comments
Detect root cause of this issue first:
Capture stack traces of crash / hang points at least. Try to play with number of threads.
Outdated versions are not supported. Try to check the latest code from master branch. |
Hi @alalek, thanks for getting back to me. I cannot run in debug mode, as I do not have access to an AMD processor to use. On all our Intel based machines there is no problem. As soon as our client runs the function on an AMD machine, it freezes. (the only difference in machines is the processor). We have tracked it down to the 'detectMarkers' function for sure, and I am having trouble debugging further then that remotely! Changing the Where can I play with number of threads? Is this a variable somewhere? Thanks again! |
I don't have access to mentioned configuration too. |
I can confirm that using |
My configuration is Ryzen 2700x (8 cores, 16 threads), Ubutu 20.04. I have successfully run tests with any number of threads (this PR #3151).
|
checked on Win10 PC with Ryzen 4600h, base ArUco tests successfully done Perhaps, your problem is related to this: #2738 The new version of OpenCV avoids this problem. |
System information (version)
OpenCV => 4.1
Operating System / Platform => Windows 64 Bit
Compiler => Visual Studio 2019
Detailed description
I have a function in my application that uses opencv and the cv::aruco module.
On machines with Intel cpus, it runs great. (tested on more than 20 PCs). On machines with AMD cpus (tested on two), it freezes and crashes the application. The only difference on the testing machines is the processor.
The crash occurs at this function:
cv::aruco::detectMarkers(InImage, dictionary5, corners, ids, detectorParams5, rejected);
I have tried rebuilding opencv and disabling AVX512 instructions in OpenCVCompilerOptimizations.cmake, and I see the same thing.
How can i solve this issue?
Steps to reproduce
Build opencv from source (4.11). Run the function
cv::aruco::detectMarkers
on a PC with an AMD threadripper Ryzen processor.The text was updated successfully, but these errors were encountered: