Haven't had any luck narrowing the culprits; when I run only one of the 5 backends you specified at a time the memory bug doesn't come up.
I've attached a copy of the most current log file. Looking through it, I noticed that it complained about being unable to find EvolutionDataServer. I did double-check and it is installed. Not sure if that's a clue. There are additional logs that I have not included (console, exceptions, etc.). Please let me know if they would be of use. Cheers. On 2/24/07, dBera <[EMAIL PROTECTED]> wrote: > > I dont think there is a package for heap-shot for ubuntu, so there isnt > much information you can provide. You can provide one valuable information > though - which index source (aka backend) is causing the memory rise. You > can shutdown beagle (using beagle-shutdown) and then restart as > $ beagled --backend name_of_backend > to start beagle with only that backend > >From index-info, you seem to be using these backends: > Files, EvolutionMail, EvolutionDataServer, Liferea, Tomboy > > You may try each of the above, one at a time to see which exact backend is > causing the behaviour. e.g. use > "$ beagled --backend EvolutionMail" > to only index the EvolutionMail data. > > Beagle has to work on a variety of data sources; unfortunately, these > memory bahevious are absent on the tests we perform on our computers. > Any help is appreciated. > > Ahh one more thing, can you attach the log directory ~/.beagle/Log/ as > tar-gz ? If its too large, then attach the files pointed to by current- > Beagle, current-IndexHelper. Thanks > > -- > beagled uses >250 Megs RAM when Idle > https://launchpad.net/bugs/87198 > -- beagled uses >250 Megs RAM when Idle https://launchpad.net/bugs/87198 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
