** Changed in: update-notifier-kde (Ubuntu)
Status: Triaged => Fix Released
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to update-notifier-kde in ubuntu.
--
k
G.Christ I can confirm.
Looks as if this is fixed in Karmic. I ran the loop of the initial post on an
up to date karmic and update-notifier "only" uses ~30Mb. On jaunty I had it
using up to and above 400Mb of RAM on the same PC.
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net
I've noticed this for some time now, I'm using Kubuntu 9.04 64 bit.
Today the update-notifier-kde is using 217 MB long after I checked for updates.
If I don't kill the process it remains until either shut-down or reboot.
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/28926
@myrtille: you are right, thanks for the tip!
But in Karmic I have seen that update-notifier-kde uses less memory,
between 20-35 MB. Right now it uses 5 MB (RSS 15 MB)
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are
Hi,
I think you can disable it by starting KPackageKit, go to settings
->Edit Software Sources->Updates and in Automatic updates uncheck
"check for updates".
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member o
I observe this bug too in jaunty 64 bit. Here what top says after only
1/2 hour uptime and one "apt-get update":
4620 pp39 19 435m 139m 25m S0 4.7 2:13.41 python
/usr/bin/update-notifier-kde
whaow...
Note that after running "apt-get update", update-notifier-kde had high
cpu usa
The big memory leak is still present in version 0.19 of Jaunty.
As a workaround until this is fixed, how can I disable update-notifier-
kde so that it doesn't start every time?
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because
In the worst case, you can kill the process yourself. It should restart
after the next sudo aptitude update.
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm raising the priority to High, since it's really bad for long running
systems (that e.g. only get suspended / hibernated).
If this cannot get fixed properly, I think a workaround should get
implemented to regularly restart the app.
** Changed in: update-notifier-kde (Ubuntu)
Importance: Med
I experience the same problem on Jaunty with KDE 4.3RC1.
running apt-get update and apt-get upgrade twice makes update-notifier-kde rack
up around 200 MB of Ram (everytime I run it, update... takes in a few more MBs.
Also for a couple of minutes it insane amounts of CPU time (in the high 70s to
btw: I've added the following snippet (in variants) to debug this (and added
output to update-notifier-kde):
(update-notifier-kde &); sleep 5; pid=$(pgrep -f ^python.*update-notifier);
echo $pid; for i in `seq 1 50`; do ps aux|grep update-notifier|grep -v
grep|grep python|awk '{print $2":"$5"/"$
This appears to be caused by apt_check / apt_check.run().
Exchanging
result = apt_check.run()
with
result = (0, 0)
in /usr/bin/update-notifier-kde prevents this growth of memory usage (there's
minor growing still though - according to ps).
apt_check is in /usr/lib/update
The issue also applies to Jaunty :
Currently the process is eating almost 100 MBs of memory.
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to update-notifier-kde in ubun
** Changed in: update-notifier-kde (Ubuntu)
Assignee: (unassigned) => Jonathan Riddell (jr)
** Tags added: pet-bug
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Mine after 1 day, 17:56:
4674 fache 39 19 130m 63m 21m S0 3.4 0:38.34 python
/usr/bin/update-notifier-kde
Not bad either, huh?
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs,
My `top` from 17 days-uptime machine:
6916 yevgen39 19 197m 124m 22m S0 3.8 1:17.20 python
/usr/bin/update-notifier-kde
Guys, please please check what's wrong with it. Thanks!
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notifi
And this is after logout/logon:
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
29856 herve 39 19 109m 43m 28m R 100 4.3 0:03.26 python
/usr/bin/update-notifier-kde
29852 herve 20 0 83768 29m 18m S0 2.9 0:00.52 python
/usr/bin/printer-applet
29807 herve 20
I did not look at the startup memory usage, but found this bug when
trying to report this program is (after plasma) the greediest on my
system:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
21946 herve 20 0 135m 66m 18m S0 6.6 16:28.16 /usr/binplasma
21995 her
** Changed in: update-notifier-kde (Ubuntu)
Status: New => Confirmed
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to update-notifier-kde in ubuntu.
--
kubuntu-
Confirmed. Kubuntu was running for about 13 days and the update-
notifier-kde process used more than 230M at the end.
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to up
I see the same problem.. I thing, after four updates is 90MB too much
for one small application.
--
Memory leak in update-notifier-kde
https://bugs.launchpad.net/bugs/289264
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to update-notifier-kde in
21 matches
Mail list logo
