Memory leak occures while using "highgui" functions (Bug #61)
Description
We get a memory leak near 4 kbytes each 10-15 seconds while using elementary highgui functions like cvQueryFrame(). The leak can start either immediatly or in 2-3 minutes after launch. This error occures also in example application "cam-histo.py" and others. Minimal code that causes the leak seems to be:
import highgui capture = highgui.cvCreateCameraCapture (0) while 1: frame = highgui.cvQueryFrame (capture)
Environment: OpenCV 2.0.0.a, Python 2.6, SWIG python bindings, Windows Vista Home Premium.
Associated revisions
Merge pull request #61 from vpisarev/bug_2509
Merge pull request #61 from ilya-lavrenov:perf_ocl
History
Updated by James Bowman about 15 years ago
Changing to "swig python"
BTW, there is a sample that uses the new Python bindings:
samples/python/camshift.py
Updated by Илья Москвин about 15 years ago
Replying to [comment:1 jamesb]:
Thanks, we know that in the new python bindings there is no leak problem. But there are some another problems, that make us to combine the old and the new bindings in one program.Changing to "swig python"
BTW, there is a sample that uses the new Python bindings:
samples/python/camshift.py
Updated by Victor Eruhimov over 14 years ago
- Status deleted (
Open)
Updated by Vadim Pisarevsky over 14 years ago
swig python bindings are not included into OpenCV anymore. Let's make the new bindings good enough for all purposes.
- Status set to Done
- (deleted custom field) set to wontfix
Updated by Andrey Kamaev almost 13 years ago
- Status changed from Done to Cancelled
- Category set to python bindings