GPU BruteForceMatcher matching function(s) leak(s) handles (Bug #1493)

Added by funkyclaude - over 13 years ago. Updated almost 13 years ago.

Status:Done Start date:
Priority:High Due date:
Assignee:Vladislav Vinogradov % Done:

0%
Category:gpu (cuda)
Target version:2.4.0
Affected version: Operating System:
Difficulty: HW Platform:
Pull request:

Description

The GPU BruteForceMatcher's "match" function leaks handles. When I call it in a loop I can see dramatical handle increase in the Windows task manager. The process' reserved memory doesn't increase but the total physical memory usage.

An example code is appended.

My setup:
Windows 7 64bit
MS Visual Studio 2008 Win64 (release build, Compiler-Version: 15.00.21022.08)
CUDA SDK / Computing Toolkit 4.0
no IPP, no TBB, no Eigen2 but Cuda

main.cpp - Minimal example (480 Bytes) funkyclaude -, 2011-11-29 03:00 pm

History

#1
Updated by Vladislav Vinogradov over 13 years ago

The problem isn't in BruteForceMatcher, but in cv::gpu::DeviceInfo constructor.

#2
Updated by Alexander Shishkov about 13 years ago

  • Description changed from The GPU [[BruteForceMatcher]]'s "match" function leaks handles.... to The GPU BruteForceMatcher's "match" function leaks handles. Whe... More

#3
Updated by Vladislav Vinogradov about 13 years ago

The problem is in cudaGetDeviceProperties function. The bug was submitted to NVidia.

  • Status changed from Open to Cancelled

#4
Updated by Anatoly Baksheev almost 13 years ago

Fixed with cuda4.2

  • Status changed from Cancelled to Done

#5
Updated by Andrey Kamaev almost 13 years ago

  • Target version set to 2.4.0

Also available in: Atom PDF