Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
nVidia drivers + OpenCL issue
See original GitHub issueApparently the recent nVidia drivers (version 410+) have an OpenCL update that seems to be causing Magick to fail.
I’ve tried it with 7.7 and 7.6.0.1 on several computers (including end-users) and the common factor in all of them is the nvidia driver update.
In code, it hangs the thread as soon as we get to any OpenCL-friendly method. If no OpenCL methods have been used, it gets stuck on Dispose() or at the end of the using statement. It happens in using statements for GetPixelsUnsafe() as well. Same pattern - dead on dispose.
Please let me know if I can provide any additional info.
Am using Magick.NET-Q16-HDRI-x64-OpenMP.
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Earlier this year we disabled NVIDIA devices by default for OpenCL due to a lot of reports about access violations: https://github.com/ImageMagick/ImageMagick/commit/506256cdb5e48435570bbcae81eb8d17de1f7b9f. But it looks like I made a mistake. Just pushed a patch to resolve this: https://github.com/ImageMagick/ImageMagick/commit/9c43e2af2a9ce851afdd27577282838c34bbc6c1. Working on a new release right now so a fix should be available very soon.
Haven’t been able to get any new useful info on this as we had to freeze the code for release soon. For safety’s sake, we now force OpenCL off on initialization. I’ll close this issue. If I find meaningful data in the future will reopen it. Thanks!