Damien Sandras a écrit :
Le lundi 24 octobre 2005 à 08:10 +0200, Julien PUYDT a écrit :Definitely a memory leak.Notice that : - top is not a good tool to see if a program is leaking - the leak could also be due to a camera problem, or to a GTK theme - it could also be a library leak - but it can ALSO be a GnomeMeeting leak
1G of memory usage for a gnomemeeting process, even mesured with top, means there is a leak somewhere.
Tracking that leak will be hard ; here are some questions that may help: - is the leak getting worse when many calls are placed/received ?- is the leak made better if video preview isn't enabled while gnomemeeting sits idle ?
- is gnomemeeting the only long-lived program on which the problem occurs ? Snark on #gnomemeeting