OCL module has memory leak created on objects by OpenCL API (Bug #2951)
Description
The memory leak is found by profiling any opencv_test_ocl test case with AMD APP Profiler on Windows.
Three types of OpenCL objects are not freed correctly, which are cl_program, cl_command_queue and cl_context.
One sample profiling trace snapshot:
Associated revisions
Merge pull request #2951 from ilya-lavrenov:tapi_ipp_filter2d
History
Updated by Vadim Pisarevsky almost 10 years ago
OpenCL code in 2.4.x was experimental; in 3.0-dev it's less so, please, try it out; feel free to reopen the bug if the problem is still valid
- Status changed from Open to Cancelled
- HW Platform set to x64
- Operating System set to Windows
- Affected version changed from branch 'master' (2.4.9) to branch '2.4' (2.4-dev)