processes started by beagle use 100% cpu

Bug #34495 reported by Stefan Bethge
32
Affects Status Importance Assigned to Milestone
beagle (Ubuntu)
Fix Released
Medium
Brandon Hale

Bug Description

As beagle uses external tools when indexing files, beagle
calls cpu intesive things like pdftotext. While beagled itself tries not to interfere with the work flow for the desktop user by using very little cpu power, pdftotext uses 100%, rendering the system unusable - characters in vim take seconds to appear. I think this is an unacceptable behaviour for a daemon
that runs in background, something that would normally lead me to uninstall beagle. Don't know what is possible to limit usage for external processes, maybe 'nice' already does it?

Revision history for this message
Sebastian Dröge (slomo) wrote :

i can confirm this behaviour. beagled should probably launch the helpers with a high nice value...

Changed in beagle:
status: Unconfirmed → Confirmed
Revision history for this message
Irios (irios) wrote :

In my computer, beagled grabs 95% of the processor and just stays there forever; the processor speed jumps maxes up, and the notebook flies through the battery in no time. "pdf2text" does not show in top, though; I believe it is the very beagled that's in fault.

Revision history for this message
Irios (irios) wrote :

By the way, it does grab 95% of the processor, but the computer remains perfectly usable all the time, the processor fan whining and the battery gauge dropping.

Revision history for this message
Celso Pinto (cpinto) wrote :

I just tried this and it worked: start beagled with --deny-backend EvolutionMail.

No being able to have beagled indexing my email is pure crap :\ but at least it now goes through all my other files.

Revision history for this message
Voteslave (voteslave) wrote :

I am using ubuntu dapper beta and since the kernal update i seem to be getting problems with intense disk and swap file activity - seems to triggered by starting an app that doesn't actually work properly - though this may not be the case in all situations

looking at system monitor there is a process called mono running 1.8gig of ram - system stabilises a bit after it loads into memory) - the 'arguments' heading reads something like "beagled-helper --debug /usr/lib/beagle/indexHelper.exe"

is it odd that it refers to an .exe file?

Revision history for this message
Sean (sean-compusmith) wrote :

Just installed the 0.2.6-1ubuntu4 update that became available earlier today on a Dapper Beta system and I have never had any problems with beagled until now. After installing the update (and re-enabling beagle -- for some reason it was disabled and not running, now I realize why) I noticed my system was significantly slower. I checked my CPU usage and it was constantly at 95 - 100%! The INSTANT I hard kill the beagled process, it drops back down to about 7 - 10%. For now, beagle is remaining disabled on my system until this major bug is fixed.

Revision history for this message
Brandon Hale (brandon) wrote :

This is a dupe of #34495, which the reporter says is fixed in Edgy and I cannot reproduce.
Closing the bug.

Changed in beagle:
assignee: nobody → brandon
status: Confirmed → Fix Released
Revision history for this message
Thom Pischke (thom-pischke) wrote :

This is NOT fixed. Every day, beagled-helper comes on and consumes 100% of my CPU for HOURS. I'm not sure it ever finishes, since I have to kill it.

Revision history for this message
Thom Pischke (thom-pischke) wrote :

Note: I'm experiencing this problem after upgrading to Edgy from Dapper. I never had this problem on Dapper.

As I write, beagled-helper has been hogging the CPU for 2+ hours. It doesn't slow down the system much, but the fan has been blasting since the thing started. The System Monitor shows that beagled-helper is Sleeping, but nevertheless using 80% of the CPU.

Revision history for this message
Rog (roger-mindsocket) wrote :

I'm experiencing this problem also, since upgrading from dapper to edgy. I have to kill -9 the beagled-helper process to get rid of it, and it comes back later unless beagle is shutdown.

Revision history for this message
SubWolf (subwolf) wrote :

Just killed beagled-helper off, like previous mentions, was consuming 100% cpu and slowing everything else down.

I do have 20 or 30 PDF's in the system, and a good 600Gb of disk space with several hundred thousand files, probably not helping.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.