Python FindHomography double free (Bug #248)

Added by Ethan Rublee almost 15 years ago. Updated almost 15 years ago.

Status:Done Start date:
Priority:Normal Due date:
Assignee:James Bowman % Done:

0%
Category:python bindings
Target version:-
Affected version: Operating System:
Difficulty: HW Platform:
Pull request:

Description

When calling FindHomography from within a function, python gives a segmentation fault after returning from the function. Attached is a test program that causes the fault on my machine. Seems to be some double free or memory corruption when debugging.

I noticed that FindFundamentalMat runs properly with the same code.

testH.py - script to replicate the bug - run with python testH.py (6.3 kB) Ethan Rublee, 2010-04-01 12:33 am

Associated revisions

Revision 512f0091
Added by Andrey Kamaev about 12 years ago

Merge pull request #248 from taka-no-me:reduce_tmp_size

History

#1
Updated by James Bowman almost 15 years ago

Function was returning H (for no good reason). This was causing reference count off-by-one error. Removed the H return.

Fixed in r2966.
Docs updated.

  • (deleted custom field) set to fixed

#2
Updated by Ethan Rublee almost 15 years ago

Thanks. Should the return be int since FindHomography in c api returns a status integer? I added int to that line, similar to FindFundamentalMat and it did return the correct status.

Also available in: Atom PDF