Advisory: EvolutionDataServer could leak memory

Problem: Since 0.2.18 (including 0.3.x releases), beagled could be
leaking memory when the EvolutionDataServer backend is enabled.

The problem has been observed when there are one or more webcal
calender items in Evolution. It is not immediately clear, but the
memory leak might be present even otherwise. The memory is leaked when
there is new data to index in Evolution; webcal sources with the
default 30 min sync rate will show the memory RSS jumping roughly
every 30 minutes.

Workaround: Disable the EvolutionDataServer backend, or as a less
severe workaround set the sync interval for the webcal calender to
something large.

Explanation: The memory leak is present in evolution-sharp and is
probably in a couple of new methods introduced in a recent
evolution-sharp. Visit for details on the
evolution-sharp bug.
I dont see any workaround in beagle. Indexing of webcal data was
temporarily disabled in svn trunk as a panic measure, but I think the
leak will happen whenever there is any new task/contact/memo etc. in
Evolution. I plan to re-enable the webcal indexing.

Debajyoti Bera @
beagle / KDE fan
Mandriva / Inspiron-1100 user

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]