> Indeed. I have restarted beagled with heap-shot and am currently at a > VmSize of 100MB.
You do not need to wait for the full run. If its grown to, say, 200 MB, you can stop it. A few snapshots (e.g. every tenth one, basically first, last and a 10 in the middle) would be helpful to know what is causing the memory rise. Also attach the log file when you do - if its size is withing attachable limit (then attach the first 2000 lines or so). I am hoping to find something in those log files. Joe is the one around here who is well versed in the black magic of heap-snapshots. I am familiar with heap-buddy but they are not suitable in this situation. Your snapshots would be a good lesson of heap-shotism for me :-). > The files each are anywhere from 350-460KB. 99 of them. A few early > ones are 0B long though due to disk space issues. You might delete the older ones - since you started the new run with better (read: worse for your computer) performance. - dBera -- ----------------------------------------------------- Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user _______________________________________________ Dashboard-hackers mailing list [email protected] http://mail.gnome.org/mailman/listinfo/dashboard-hackers
