> > Argh... only if you started with --heap-shot :-(. This sounds like a > > perfect setup for figuring out what keeps on eating the memory. > > OK. So it's dead now. What arguments exactly do you want me to start > it with? > > Just "beagled --heap-shot --bg"?
You said you generally dont build from source these days. So I didnt want to scare you before :( - but if you are serious, 1) you need to install heap-shot http://svn.myrealbox.com/viewcvs/trunk/heap-shot/ (there is a download tarball link at the bottom) 2) export BEAGLE_HEAP_SHOT_DIR=/tmp 3) Start beagled with --heap-shot 4) Heap-shot allows to checkpoint the heap status at several times by sending $ kill -PROF <pid of beagled> while beagled is running, sending the signal PROF to beagled dumps the current heap map to a file in /tmp. Take a few snapshots and then send them to me. They should be somewhat useful. For baseline reference, take a snapshot when beagle starts indexing and then maybe 1 every 100 MB. - 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
