2017-03-10 02:04:05 -0600 | received badge | ● Editor (source) |
2017-03-10 02:02:00 -0600 | commented question | OpenCL access violation with x64/MSVC2015 Updating the graphics driver has cured the problem. Thanks to LBerger for pointing me in the right direction. |
2017-03-10 01:40:49 -0600 | commented question | OpenCL access violation with x64/MSVC2015 Intel(R) HD Graphics 530 (on a Dell Precision 7510 laptop). Dell may have used a custom variant for them. |
2017-03-09 04:56:55 -0600 | asked a question | OpenCL access violation with x64/MSVC2015 I'm a new user of openCV. Having built the .dlls on MSVC2015, targeting x64, I get the following error when trying to run a test program QuickView.exe. } The error I get is exception thrown at 0x000007FEDD58A32A (igdrcl64.dll) in QuickView.exe: 0xC0000005: Access violation reading location 0x0000000000000990. I can apparently continue past the error with no ill effects. The call stack is (with apologies for the line length) Obviously imshow is calling something deep within OpenCL that is giving a problem. The workarounds I have successfully tested are to compile OpenCV without OpenCL support (comment out line 124 in cvconfig.h), or to switch off Win32 Access Violation catching. However, neither of these seem very satisfactory. Can anyone suggest a proper remedy, please? |
2017-03-08 04:41:10 -0600 | answered a question | Exception thrown at 0x000007FEFDB49E5D in CVpro1.exe: Microsoft C++ exception: cv::Exception at memory location 0x000000000023F320. I'm seeing a similar problem on MSVC 2015, running the image viewer test code: I'm building my own OpenCV libraries for x64. I get an exception when I run under the MSVC debugger. It seems to be in the initialization before any of the main code is executed. However, I can continue past it without any apparent problems. The program also runs fine under Windows CMD shell. Looking at the stack when the exception is thrown, it is a call to OpenCL: opencl_fn3(OPENCL_FN_clGetPlatformIDs, cl_int, (cl_uint p1, cl_platform_id* p2, cl_uint* p3)) One solution I've tested is to disable OpenCL (comment out line 124 of cvconfig.h) and rebuild the libraries. This avoids the call that is causing the problem, but is unsatisfactory because one loses the power of openCL. Another workaround is to disable the Win32 access violation exception from being caught by the debugger. (When I see the exception it opens an "Exception Settings" window which allows me to select the kinds of exceptions that MSVC breaks for). However, disabling exceptions like this feels unsafe to me. However, neither of these feels like a permanent solution. Maybe someone with deeper MSVC/OpenCV/OpenCL knowledge can sort it out - I'm a complete newbie to OpenCV. |