setxel and setxela on PNMImage leak memory
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Panda3D |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Both the setxel and setxela methods on a PNMImage object leak memory, this is using the Python version of panda. I found this bug a while ago, and found that the memory leaking was definitely in the setxel and setxela methods. We were creating 100 or so dynamic textures and were calling setxel a lot, and in no time the machine ran out of memory. We found that the issue was definitely in the setxel and setxela methods and at the time, we worked around the problem by using a second image and calling copysubimage, which does not leak memory. Sorry, I don't have any sample code at the moment, but all you really need to do is write a quick function that creates a PNMImage and fills it using setxel, then destroy the PNMImage, call the function lots of times and you see the memory leaking away. comment out the setxel part, and the leak goes away.
OS: Ubuntu 9.10, 32 bit
Panda: 1.6.2
Unable to reproduce. Please reopen with sample code if the bug is still present.