The problem for me is that it uses too much memory. Using a 1.5GB
resident set (of 3.0GB total virtual) on a 2GB system means that
everything else has to use swap, even if you're at +19 nice. And when
IO is highly-contended already, even swap is slower than usual. It's
actually so bad I'm losing
On 20/02/2008, Thom Pischke <[EMAIL PROTECTED]> wrote:
> Well, --reindex didn't seem to help anything. In my experience thus far
> on hardy, tracker is usually either indexing or displaying the '!'
> symbol, so I've just uninstalled.
Same.
--
Martin
--
Tracker consumes more then 90% of CPU
Well, --reindex didn't seem to help anything. In my experience thus far
on hardy, tracker is usually either indexing or displaying the '!'
symbol, so I've just uninstalled.
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
You received
No, haven't bothered reporting it, figured it was just alpha hiccups.
I'll try --reindex and see if it behaves itself, though if there are
really corrupt DBs from earlier versions, seems like the package update
ought to trigger a reindex automatically.
--
Tracker consumes more then 90% of CPU eve
Thom,
have you reported the crashes in trackerd? (crashes in tracker-extract
are irrelevant as it will self destruct if it takes too much memory or
takes too long to extract metadata this is a deliberate feature and not
a bug!)
wrt not working - this could be because of bugs in the DB from 0.6.
For me, tracker crashes at least daily on hardy, but maybe that's
because it's still alpha. Tracker is definitely a net-minus for daily
use in hardy right now, will probably just uninstall it at some point if
it doesn't stabilize. Most of the time when I try to actually use it,
it doesn't work an
if trackerd is not shut down cleanly it will call sqlite to do a
corruption check.
This corruption check is very cpu heavy and Im thinking about removing
it due to the load it causes.
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
Y
i have a new installation with 8.04 hardy: same problem:
tracker consumes all cpu (despite saying it is in state 'sleeping').
this is after the system was sitting idle for a day, thus all available files
should have been indexed.
please fix, or make it at least not default setting: it is a huge
Running trackerd 0.6.3 with indexing and watching enabled at throttle
level 20, it gets stuck and uses ~90% of one core perhaps a minute or
two after launching. strace shows the following output:
poll([{fd=11, events=POLLIN}, {fd=16, events=POLLIN}, {fd=13, events=POLLIN}],
3, 1998) = 0
gettimeo
The problem still persists on my machine with the latest updates, why is
the status fixed released?
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
I had a similar problem this afternoon. tracker was using up between 40-48% of
the cpu power, and was slowly the system down very visibly. After adjusting
tracker-settings for lower cpu usage, the problem seemed to be alleviated. A
check at the tracker log showed showed a huge stream of errors f
Trackerd consumes a lot of CPU mainly when I'm downloading something. I
notice it most obviously when using KTorrent. It's as if trackerd sees
the change to some blocks of the file and has to rescan the whole thing,
over and over again. Since the file is continually modified, as long as
anything
tracker (0.6.3-0ubuntu1) gutsy; urgency=low
[ Emilio Pozuelo Monfort ]
* New upstream release (LP: #130794, #131983, #132320, #137352, #138331,
#139173, #132505, #131559, #131735, #132710, #133246, #137873, #138778.
* debian/patches/01-version_fix.patch,
debian/patches/02-getenv.patc
Retargeting as this won't make Beta release. We will upload a new
tracker release with a fix for this right after beta release, when the
freeze isn't in place anymore.
** Changed in: tracker (Ubuntu)
Target: ubuntu-7.10-beta => ubuntu-7.10-rc
--
Tracker consumes more then 90% of CPU even
Jamie is releasing 0.6.3 this week (possibly on 20th). I'll take care of
packaging it.
** Changed in: tracker (Ubuntu)
Assignee: (unassigned) => Emilio Pozuelo Monfort
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
You received
Fixed in svn (option is not live yet though so will only take effect
when tracker is restarted - will make options live very soon)
** Changed in: tracker (Ubuntu)
Status: Confirmed => Fix Committed
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launch
** Changed in: tracker (Ubuntu)
Importance: Undecided => Critical
Target: None => ubuntu-7.10-beta
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
You received this bug notification because you are a member of Ubuntu
Bugs, w
we will fix this soon... (I dont have permission to change priority)
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Can someone set the priority for bug to critical
--
Tracker consumes more then 90% of CPU even when indexing is disabled
https://bugs.launchpad.net/bugs/132320
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I've killed trackerd (SIGKILL, as SIGTERM doesn't work), so I don't know
what tracker-status would've told me.. but I told tracker not to index
or watch, so it shouldn't be doing any of these things (I don't think it
should even start if both are disabled, it's kind of pointless to have
it running
20 matches
Mail list logo
