Comment 5 for bug 544595
Revision history for this message
| Tristan Brindle (tristan-brindle) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
There are several possible things going on here. The most likely is that OggConvert isn't destroying the instance of the Transcoder class after transcoding is complete (because Python isn't garbage-collecting it). An easy way to test this is to transcode a video, let the memory use grow, and then when it's finished, start transcoding another video without restarting OggConvert, and see what happens.
There are a few other possibilities, but I'm not sure how likely they are.
As to the amount of memory used... well, OggConvert itself (the GUI) uses around 12MB or so on a 32-bit system, a bit more on 64-bit. The rest is used by GStreamer during the transcoding process. I have to say I'm surprised at the amount of memory it seems to be using -- it's possible that a memory leak has sneaked in to one of the GStreamer elements that OggConvert uses. On the other hand, if you're transcoding to Dirac, this memory use is more-or-less normal -- schroenc uses a lot of RAM to speed up encoding.