Memory Leak in FillPoly using Python (Bug #2187)

Added by Andreas Bigontina over 12 years ago. Updated over 9 years ago.

Status:Open Start date:2012-07-24
Priority:Normal Due date:
Assignee:Vadim Pisarevsky % Done:

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

Description

Hi OpenCV-Team,

it seams like there is a memory leak in the cv.FillPoly method.
We discovered it using Python and OpenCV 2.3.1 and tested it with 2.4.2 as well.

You can easily reproduce the leak like this:

1import cv
2img = cv.LoadImage("someimage.jpg")
3poly = tuple([(100,100),(150,150),(100,200),(50,150)])
4for i in range(1,1000000):
5    cv.FillPoly(img, [poly],(25,255,55))
6    print i

I hope its not too hard to solve, since its a really big problem for our project.

Regards,

Andreas

History

#1
Updated by Marina Kolpakova over 12 years ago

  • Target version set to 2.4.3
  • Category set to python bindings

#2
Updated by Andrey Kamaev over 12 years ago

  • Assignee set to Vadim Pisarevsky

#3
Updated by Andrey Kamaev over 12 years ago

  • Target version changed from 2.4.3 to 3.0

#4
Updated by abid rahman over 11 years ago

Hi @Andrey Kamaev,

Can I know details of this problem?

1. `cv` interface is going to be removed in 3.0 anyway.
2. Also in `cv2` (compiled from master branch), it is working fine for me.

#5
Updated by Maksim Shabunin almost 10 years ago

Can not reproduce on master branch version 3.0-rc1. Moving to 2.4 branch.

  • Target version changed from 3.0 to 2.4.12
  • HW Platform set to Any
  • Operating System set to Any
  • Affected version set to 2.4.0 - 2.4.8

#6
Updated by Maksim Shabunin over 9 years ago

Issue has been transferred to GitHub: https://github.com/Itseez/opencv/issues/4398

Also available in: Atom PDF