Re: IndexHelper eating cpu

> > For update, the file above turned out to be a jpeg file which was causing
> > a loop in the jpeg handling routine. It is basically the same as
> >
> > and has been fixed in svn trunk in r3408.
> Post 0.2.16?  I guess I am pretty screwed to run beagle (unless I build
> my own package) until the next release then?

In a way, yes. Beagle borrows some code from F-Spot (thanks guys!) for dealing 
with images. The problem was traced in the F-Spot code, promptly fixed there 
and then fixed in our local copy. It is part of Util.dll, so I cannot even 
build a jpeg filter binary for you.

There is a workaround if you can live without indexing jpegs.
Add this to /etc/beagle/external-filters.xml,


This will _ignore_ all jpeg files, on disk, in archives, emails etc. The bad 
part is, due to some technical limitations, when you get the next version 
with fixed jpeg filter, you have to delete your index for beagle to re-index 
the jpeg files.

> I seem to have another CPU gobbling beagled-helper but when I signal it
> with USR2 it reports:
> 20070210 08:06:48.1626 19961 IndexH  WARN: Filtering status (9h39m25s ago):
> determining filter for email://5/INBOX/sent;uid=18341#1
> Is this the same issue?

Could be. If the attachment is jpeg, then most likely it is fixed in trunk. 
Otherwise, it is some other filter bug.

- dBera

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

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