Updated by Andrey Kamaev about 13 years ago
The usually black images created with @cv.CreateImage@ cv.CreateImage gets corrupted after a @tostring()@ tostring() conversion: random white pixels appear and @CountNonZero@ [[CountNonZero]] returns >0.
After iteration, the @CountNonZero@ [[CountNonZero]] grows and grows.
I wrote a testcase to demonstrate this behavior. behaviour. It would be nice if you could add it to the source tree.
All default python-bindings test cases are OK on my system.
I suspect this causes segmentation faults and memory corruptions in more complicated and iterated usages. I couldn't reproduce these segfaults in a test case, anyway it's quite obvious that if the image memory space gets corrupted, other parts of the memory may be damaged as well.
See attached file.
After iteration, the @CountNonZero@ [[CountNonZero]] grows and grows.
I wrote a testcase to demonstrate this behavior. behaviour. It would be nice if you could add it to the source tree.
All default python-bindings test cases are OK on my system.
I suspect this causes segmentation faults and memory corruptions in more complicated and iterated usages. I couldn't reproduce these segfaults in a test case, anyway it's quite obvious that if the image memory space gets corrupted, other parts of the memory may be damaged as well.
See attached file.