Re: beagled-helper maxing out CPU core

Joe Shaw wrote:
>> And saw this resultant output in ~/.beagle/Log/current-IndexHelper:
>>
>> 20080812 09:55:23.7245 04698 IndexH  WARN: Handling signal 12 (SIGUSR2)
>> 20080812 09:55:23.7614 04698 IndexH  WARN: Filtering status (2h54m13s ago):
>> no document is currently being filtered.
>>     
>
> So, I think the error message here is a little bit misleading.  I
> think in this case it means not that no document is being filtered but
> that it's trying to determine the MIME type for the document, and it's
> that code (possibly inside xdgmime) that is spinning.
>
> You might be able to better track down the problematic file by looking
> at /proc/fd/4698 and look for files that are open that it's likely
> crawling.  You could then run beagle-extract-content on those files
> and see if you can easily reproduce the CPU issue.

The only open file I saw that looked suspicious was 
~/.gnome2/f-spot/photos.db.  But all I get when I run 
beagle-extract-content on that is this (which runs very quickly, of course):

Filename: file:///home/sandy/.gnome2/f-spot/photos.db
Debug: Loaded 63 filters from /usr/lib/beagle/Filters/Filters.dll
Debug: Verifying filter_cache at /home/sandy/.beagle/filterver.dat ... 
cache is dirty ? False
Debug: No filter for file:///home/sandy/.gnome2/f-spot/photos.db 
(/home/sandy/.gnome2/f-spot/photos.db) [application/x-sqlite3]
No filter for application/x-sqlite3


Complete output of ls -l /proc/4698/fd is below, if that helps:

sandy@linux:~> ll /proc/4698/fd
total 0
lr-x------ 1 sandy users 64 2008-08-12 13:19 0 -> /dev/null
l-wx------ 1 sandy users 64 2008-08-12 13:19 1 -> 
/home/sandy/.beagle/Log/2008-08-12-06-59-27-IndexHelper
l-wx------ 1 sandy users 64 2008-08-12 13:19 10 -> pipe:[98847]
lr-x------ 1 sandy users 64 2008-08-12 13:19 11 -> pipe:[98848]
l-wx------ 1 sandy users 64 2008-08-12 13:19 12 -> pipe:[98848]
lr-x------ 1 sandy users 64 2008-08-12 13:19 13 -> pipe:[98849]
l-wx------ 1 sandy users 64 2008-08-12 13:19 14 -> pipe:[98849]
lrwx------ 1 sandy users 64 2008-08-12 13:19 16 -> socket:[16485]
lr-x------ 1 sandy users 64 2008-08-12 13:19 17 -> /tmp/tmp53d12170.a2w
lrwx------ 1 sandy users 64 2008-08-12 13:19 19 -> 
/home/sandy/.beagle/TextCache/TextCache.db
l-wx------ 1 sandy users 64 2008-08-12 13:19 2 -> 
/home/sandy/.beagle/Log/2008-08-12-06-59-27-IndexHelper
lr-x------ 1 sandy users 64 2008-08-12 13:19 20 -> /dev/urandom
lrwx------ 1 sandy users 64 2008-08-12 13:19 21 -> socket:[17379]
lrwx------ 1 sandy users 64 2008-08-12 13:19 22 -> 
/home/sandy/.gnome2/f-spot/photos.db
lr-x------ 1 sandy users 64 2008-08-12 13:19 24 -> /tmp/tmp37d35d24.a2w
lr-x------ 1 sandy users 64 2008-08-12 13:19 25 -> /tmp/tmp324142c0.a2w
lr-x------ 1 sandy users 64 2008-08-12 13:19 26 -> /tmp/tmp1b04f823.a2w
lrwx------ 1 sandy users 64 2008-08-12 13:19 27 -> 
/home/sandy/.beagle/TextCache/TextCache.db-journal
lr-x------ 1 sandy users 64 2008-08-12 13:19 28 -> 
/home/sandy/.beagle/TextCache
l-wx------ 1 sandy users 64 2008-08-12 13:19 29 -> 
/home/sandy/.beagle/Log/2008-08-12-06-59-27-IndexHelperExceptions
l-wx------ 1 sandy users 64 2008-08-12 13:19 3 -> 
/home/sandy/.beagle/Log/2008-08-12-06-59-27-IndexHelper
lr-x------ 1 sandy users 64 2008-08-12 13:19 4 -> /dev/null
lr-x------ 1 sandy users 64 2008-08-12 13:19 5 -> pipe:[16477]
l-wx------ 1 sandy users 64 2008-08-12 13:19 6 -> pipe:[16477]
lr-x------ 1 sandy users 64 2008-08-12 13:19 7 -> pipe:[98846]
l-wx------ 1 sandy users 64 2008-08-12 13:19 8 -> pipe:[98846]
lr-x------ 1 sandy users 64 2008-08-12 13:19 9 -> pipe:[98847]