@tuannhtn my release built program can run without error, but I find that the memory keeps increasing as I keeps running codes multiple times, I'm worried maybe it will crash down at some point.

Thank you very much for your suggestion, but can memory leaks be detected under release mode? anyway, my .libs under release mode have always been those .libs without 'd' attached to the tail just like you suggested.

Yes, those .h .lib and .bin files are pre-compiled files, you can directly use them as long as you have the latest visual studio IDE, or you will have to compile all those files by yourself using CMake, please refer to:

http://docs.opencv.org/trunk/doc/tutorials/introduction/windows_install/windows_install.html

http://docs.opencv.org/trunk/doc/tutorials/introduction/windows_visual_studio_Opencv/windows_visual_studio_Opencv.html#windows-visual-studio-how-to

they will tell you step by step how to use OpenCV.

@StevenPuttemans Sorry about that, edit and add an update, got it, thank you very much.

Problem hasn't been solved yet, can anybody offer some helps on this?

Problem hasn't been solved yet, can anybody offer some helps on this?

By the way, I've tried both pre-compiled libs and libs compiled by myself, memory leaks detected in both cases.

@wl2776 thank you for your suggestion, I've blocked all C includes, and installed VLD, its header file vld.h is included in stdafx.h, now codes in stdafx.h looks like this:

include "opencv2/opencv.hpp"

include "opencv2/nonfree/nonfree.hpp"

include <vld.h>

but I still got memory leak detected by IDE, not by VLD, VLD reported no memory leak:

{135} normal block at 0x00874CA8, 61 bytes long. Data: < ( (M 0L > 00 00 00 00 28 00 00 00 28 4D 87 00 30 4C 87 00 {134} normal block at 0x00874C30, 56 bytes long. Data: < ( L > 00 00 00 00 28 00 00 00 A8 4C 87 00 00 00 00 00 Object dump complete. No memory leaks detected. Visual Leak Detector is now exiting.

P. S. I didn't press Feat button, i.e. OnFeat() hasn't been triggered.

I've created a completely empty new visual studio 2010 MFC project just trying to test the latest opencv 2.4.8, I added some header files to the stdafx.h as shown below:

and added corresponding libs to the linker:

then I added a menu non-popup button "Feat" to carry some testing codes of mine, only two lines:

compiling and linking are both successful, but when I close the program, memory leak happens no matter I pressed button "Feat" or not:

It's pretty weird to me, since even when I don't go into the OnFeat(), no cv::Mat are instantiated, there are still memory leaks detected. There will be no memory leaks only when I delete these two lines of codes in OnFeat(), I've also tried if I only instantiate a cv::Mat in OnFeat() not imread any images, there are still memory leaks detected no matter I go into the OnFeat() or not, but much less, as shown below:

Has anybody encountered this kind of problem? Could it be the way I used opencv? am I doing something totally wrong with opencv? P. S. I've also tried 2.4.7, still has the same problem.