Function "FindContours" crashes with both SWIG and new python bindings (Bug #81)
| Status: | Done | Start date: | |
|---|---|---|---|
| Priority: | Blocker | Due date: | |
| Assignee: |  James Bowman |
% Done: | 0% |
| Category: | python bindings | ||
| Target version: | - | ||
| Affected version: | Operating System: | ||
| Difficulty: | HW Platform: | ||
| Pull request: |
Description
Function "FindContours" causes application crash when we call it in the main thread as well with new python bindings as with SWIG bindings. When we use this function in a new thread an application crash occurs only with new python API. This is about WinVista, and in WinXP "FindContours" crashes always.
Environment: OpenCV 2.0.0.a, Python 2.6, 2 different mashines with Windows Vista Home Premium and Windows XP Pro SP3.
Associated revisions
Merge pull request #81 from stephenfox/master
update openni sample comments referring #81
update openni sample comments referring #81
History
Updated by anonymous - about 15 years ago
I think I have the same problem using the new python API. When I call FindContours on a black image, it returns a cvseq that generates a 'segmentation fault' when accessed. This is both in the 2.0 and SVN version.
Updated by Gijs Molenaar about 15 years ago
Addition to my anonymous post above:
Note that when FindContours can find contours it returns a valid cvseq. I tested it with Ubuntu Linux 9.10 64 bit and Mac OS X 10.6.
BTW: Sorry I try to log in with my registered ROS account, but this doesn't work. I don't know where to report this.
Updated by James Bowman about 15 years ago
On this.
Updated by James Bowman about 15 years ago
Regression and fix in r2635.
- (deleted custom field) set to fixed