Monday, April 20th, 2009, 1022 days ago
Rules of memory management of openCV
After several weeks’ hard working, finally, the memory leaking problem is fixed.
In the last post which listed nearly all kinds of variaties declare and delete methods, here i add several tips for memory check while it is leaking:
1) int, double, float … : these kinds of variaties don’t matter so much;
2) IplImage* : this really matters, especially when cvCloneImage is conducted, if the destination variaty was not cleared, the memory would fly up.
3) CvMemStorage: be careful, to delete this data you have to use not ‘cvReleaseData’ but ‘cvReleaseMemStorage’, one declaration, one delete operation.
POSTS MAY BE OF INTEREST
- Doing openCV in pandaboard 3 – successful installation
- Doing openCV in Pandaboard
- Hand gesture recognition for HCI
- Hand detection and image recognition
- Coming soon: A review of openCV detection & recognition
- Pattern recognition and applications
- Object tracking using AS3
- Interactive table
- Touchable holography
- About the codes sharing
- Usability of comsumer electronic products
- Color recognition using openCV 2
- Recognizing circles accurately
- Do we need more novel interaction methods?
- Hand detection using openCV
