The last week or two, Gconfd has started taking noticeably large amounts of memory and swap, to the point that over 24 hours, my system is running quite tight on memory (I have 512 MiB RAM, 512 MiB swap.) Latest report is 134 MiB of memory, 23.4 MiB resident, which to me leaves a suspicion that it is leaking memory (what was the first hint, Sherlock? ;) rather than just a vigorously developing database of programs and interactions - my .gconf directory is only 2.3MiB. This is version 1.2.1-3 (ie. testing.) Am I the only one running into this? This is not the same as bug #149176, as this builds slowly over time, and definitely does not "reset to zero", although it has resulted in some daemons exiting because they couldn't get necessary memory. -- Mark L. Kahnt, FLMI/M, ALHC, HIA, AIAA, ACS, MHP ML Kahnt New Markets Consulting Tel: (613) 531-8684 / (613) 539-0935 Email: kahnt@hosehead.dyndns.org
Attachment:
signature.asc
Description: This is a digitally signed message part