What is going on? Please make last 32-bit Ubuntu Kubuntu Lubuntu Xubuntu 18.04
usable out of box for everyone who will now come with old laptops to use 32-bit
version.
Remove this bad package. Who is trolling and not allowing fix implemented?
I just installed old Laptop and on each start
I think this bug is Ubuntu-specific. It never happend since I'm using
Devuan/Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
This bug was reported way back in 2009 . Today it's 1st June 2020 and
this bug is still here kubuntu 18.04 . This background process fires up
a few seconds after i turn on my laptop and continues to consume 100% of
both the cores and after a minute or so when it stops . Python3 would
then start
Th bug was reported in 2009 and in Kubuntu 18.10 the bloody thing is
still making my laptop unusable for several minutes every day after boot
although it's not even in cron.daily. It is super annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Kubuntu 18.04, again the problem has not been solved, sometimes I find myself
the laptop or desktop that slows down, looking through the processes there is
always the process "apt-xapian-index" that uses CPU.
I resolve by removing the package, but it pulls other dependencies:
** Changed in: apt-xapian-index (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
Still happily chewing CPU cycles on 16.10.
Another pretty effective workaround might be: apt-get remove --purge
apt-xapian-index
The downside (on Kubuntu) it's that it takes out also muon, but if you
don't depend on it, it makes a terrific difference on your laptop
battery life.
--
You
Assuming there's no way that u-a-x-i can be re-written to avoid using so much
ram, and so much CPU, the "stutter" kludge above makes it clear that it it
ought to have sleeps in it. Use of nice (should be nice -19, in my book) and
ionice have reduced the problem, but the
bug should still be
Confirming that this is still a bug in Ubuntu 16.04.1 LTS (Xenial
Xerus). Tested on a Pentium III Mobile 1GHz w/ 1GB ram. (Compaq Evo
N600c).
Also, I note that this bug has been open for seven years and offer a
workaround that solves the problem for me. Since the update-apt-xapian-
index process
Confirming this issue with Ubuntu 14.04.4 LTS on HP 630.
apt-xapian-index in /etc/cron.weekly uses 100% of my CPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
Confirming this issue with Ubuntu 14.04.3 LTS on an AWS t2.nano instance (only
512MB RAM).
The weekly cron job that is set up by default runs ~24h after machine creation
and completely hogs the instance for more than 2 minutes.
IMHO: A process which is setup by default should not be so greedy.
Does anybody actually know if this is a flaw of some settings, or the
xapian engine by design? There are so many database and indexing systems
out there, I can't get it why this single indexing job behaves so bad
since years.
--
You received this bug notification because you are a member of
This is still a problem in 16.04 LTS.
This process uses 100% CPU for a long time and up to 500MB of RAM on my
machine. That's completely unacceptable.
Maybe now when Ubuntu switched to GNOME Software is a good time to add
the --update option to both cron.weekly and cron.daily.
--
You received
* 2016-04-03 23:40 GMT+03:00 fyo wrote:
>
> That's not what the diff says. There is no change in ionice behavior in
> this patch. The patch removes --update from both branches of the if-
> statement.
Thanks for pinpointing that to me, fyo -- somehow I have mixed these
four lines (and --update +
> I still fail to see how removing ionice binary (a disk I/O scheduler)
from the index rebuilding can possibly change DB modification type
That's not what the diff says. There is no change in ionice behavior in
this patch. The patch removes --update from both branches of the if-
statement.
--
* 2016-04-02 23:43 GMT+03:00 fyo wrote:
>
>> fyo, do you mean this statement:
>
>> > - do not modify the DB "in-place" with --update to avoid
>> > software-center seeing a corrupted database when it has
>> > it open at the same time
>
> Yes, that appears to be the argument for removing --update,
> fyo, do you mean this statement:
> > - do not modify the DB "in-place" with --update to avoid
> > software-center seeing a corrupted database when it has
> > it open at the same time
Yes, that appears to be the argument for removing --update, which was
otherwise added in an upstream patch.
It
* 2016-03-31 10:12 GMT+03:00 fyo wrote:
>
> Agree or disagree, you can see the reason for the WONT FIX here:
> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/apt-xapian-index/wily/revision/22
fyo, do you mean this statement:
> - do not modify the DB "in-place" with --update to avoid
This bug has been fixed upstream as of April 2010, but for some reason
NOT in any of the Ubuntu packages since.
upstream:
http://anonscm.debian.org/cgit/collab-maint/apt-xapian-index.git/tree/debian/cron.weekly
ubuntu:
The suggested fix and the currently applied fix differ in one important
aspect: The --update option has been dropped.
tldr: Unless --update is broken (and it doesn't appear to be), it should
be included in the fix as it reduces run time quite significantly.
To estimate the effect of --update I
Why not just limit this to 20% maximum of 1 core and 5% of memory?
(14.04.2 LTS here). no one would even otice this any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
This happened to me today on XUbuntu 15.04 final with updates. It seems
to stay on hogging as much as CPU as it can get its hands on (nice 10
apparently) and using about as much memory as stated earlier here. It
just keeps on hogging, making me wonder if something's gone wrong.
I probably can
Reproduced on daily build of XUbuntu 15.04 kernel 3.19.0-12-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
To manage
My 12.04.5 LTS occasionally grinds to a halt with login nearly
impossible. Finally I caught this remote embedded 256Mbyte system in
the act and found update-apt-xapi had driven the machine well into swap.
Hopefully apt-get remove apt-xapian-index will prevent this happening
again until this
** Changed in: apt-xapian-index (Ubuntu)
Assignee: froedric (anjohnson) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and
** Changed in: apt-xapian-index (Ubuntu)
Assignee: (unassigned) = froedric (anjohnson)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and
Bralam's comment is irrelevant.
I just encountered the problem with LUbuntu 13.10 32-bit, after installing
Ubuntu Software Center. I then replicated on Ubuntu 13.10 32-bit.
System stats once update-apt-xapian-index begins: 99% CPU usage on FOUR CORES
with 257MB of memory used by the process
The usage is *by-design*. It was designed to not hog the CPU.
update-apt-xapian-index uses too much CPU
I'm lost in these arguments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
Please, fill new bug reports if you still find this issue. The usage is
*by-design*. It was designed to not hog the CPU.
** Changed in: apt
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug encoutered in 14.04 (dev branch) also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
To manage notifications about this bug
Encountered this on a fresh instance of raring immediately after
installing and updating apt-file. sudo apt-file purge immediately fixed
the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm this bug is still affecting Ubuntu 12.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
To manage notifications
Yup, this exists in 13.04 all right.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
To manage notifications about this bug go to:
I just stumbled on this bug today in raring. So, I confirm that the bug
is still not fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and
On an idle system with 512M memory and 768M swap, while /etc/cron.weekly
/apt-xapian-index was running, I used free to see memory and swap used.
It rose to then peaked at this:
total used free
Mem:503528 497736 5792
Swap: 786428 231196
I added my above comments to bug 655831
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/363695
Title:
update-apt-xapian-index uses too much CPU and memory
To manage notifications about this bug go
36 matches
Mail list logo
