BRISK runs out of memory on iOS

asked 2012-09-20 01:42:32 -0600

Bernhard
81 ●1 ●6

updated 2012-09-20 02:40:45 -0600

Hi, i tested the newly introduced BRISK detector/extractor https://github.com/Itseez/opencv/blob/master/modules/features2d/src/brisk.cpp

When i run BRISK on a little demo app keypoints are detected and extracted, but also memory warnings pop up. I've done some profiling and it seems the kernel generation (https://github.com/Itseez/opencv/blob/master/modules/features2d/src/brisk.cpp#L230) consumes a lot of memory and causes the issues.

Has anyone else spotted the same behavior (especially on mobile devices)?

bernhard

edit retag flag offensive close merge delete

add a comment

1 answer

Sort by » oldest newest most voted

answered 2012-09-20 04:03:20 -0600

Michal Kottman
71 ●1 ●3

Have you tried the Fast Retina Keypoint (FREAK) descriptor instead of BRISK? It is newer, partly based on BRISK and has some benefits, such as lower memory usage and faster descriptor calculation. You can read the details of the descriptor in this paper. It is implemented in OpenCV, so it should be simple to replace BRISK by FREAK.