Comment 5 for bug 87198

Revision history for this message
Jonathan Michaels (jhmichaels) wrote : Re: [Bug 87198] Re: beagled uses >250 Megs RAM when Idle

In the 3 hours and 15 minutes since I booted this morning, I've seen beagled
memory usage slowly inch it's way up to the following:

Virtual: 249.2
Resident: 193.7
Writable: 182.8
Shared: 11.3
Memory: 182.8

I haven't noticed any ties between specific apps or activities and a climb
in memory usage but, rather, a slow but steady progression. Once memory
usage goes up it never goes down again.

Past experience tells me that, on this system, memory usage will eventually
top out at around 280 megs.

I am not using Thunderbird. The output of beagle-info --index-info and
beagle-info --status follows:

-----------------------------
jonathan@laptop:~$ beagle-info --index-info
Index information:
Name: EvolutionMail
Count: 11400
Crawling: False

Name: EvolutionDataServer
Count: 227
Crawling: False

Name: KMail
Count: 0
Crawling: False

Name: Files
Count: 91068
Crawling: True

Name: GaimLog
Count: 0
Crawling: False

Name: IndexingService
Count: 0
Crawling: False

Name: Tomboy
Count: 80
Crawling: False

Name: Labyrinth
Count: 0
Crawling: False

Name: Blam
Count: 0
Crawling: False

Name: Liferea
Count: 577
Crawling: False

Name: Akregator
Count: 0
Crawling: False

Name: KonquerorHistory
Count: 17
Crawling: False

Name: KonqBookmark
Count: 0
Crawling: False

Name: KNotes
Count: 0
Crawling: False

Name: KOrganizer
Count: 0
Crawling: False

Name: KAddressBook
Count: 0
Crawling: False

Name: Kopete
Count: 0
Crawling: False

Name: Konversation
Count: 0
Crawling: False

Name: applications
Count: 293
Crawling: False

Name: documentation
Count: 3946
Crawling: False

---------------------------

jonathan@laptop:~$ beagle-info --status
Scheduler:
Count: 6383
Status: Waiting for the next trigger time

Pending Tasks:
Scheduler queue is empty.

Future Tasks:
Maintenance 0 (2/23/2007 1:45:52 PM)
Optimize FileSystemIndex
Hold until 2/23/2007 1:55:52 PM

---------------------------

In the few minutes it has taken me to write the above, memory usage has
climbed to 191.2 megs.