Bug#802306: packagekitd eating up RAM

Hi Matthias, On Sat, 13 Feb 2016 16:33:05 +0100, Matthias Klumpp wrote: > Can you check if this issue still appears with the latest PackageKit > in unstable (v1.1.0)? > I fixed a few minor memory leaks that I found, and there are also a > few other changes which might have

Bug#802306: packagekitd eating up RAM

Hi! Can you check if this issue still appears with the latest PackageKit in unstable (v1.1.0)? I fixed a few minor memory leaks that I found, and there are also a few other changes which might have an impact on this - although I am still a bit in the dark on why this issue happens at all (still

Bug#802306: packagekitd eating up RAM

Package: packagekit Version: 1.0.11-2 Followup-For: Bug #802306 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, This still exists in 1.0.11-2. - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1,

Bug#802306: packagekitd eating up RAM

Package: packagekit Version: 1.0.10-1 Followup-For: Bug #802306 Me too, Currently packagekit is eating about 6GB of memory. I ran strings on the core file and the following bunch keeps repeating: -- WwanHardwareEnabled WimaxEnabled WimaxHardwareEnabled ActiveConnections PrimaryConnection

Bug#802306: packagekitd eating up RAM

Package: packagekit Version: 1.0.11-1 Followup-For: Bug #802306 Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of

Bug#802306: packagekitd eating up RAM

Does this problem also appear when running PK on the command-line? Please install the packagekit-dbg package and valgrind, then kill the running packagekitd daemon and run the following command in a terminal session: sudo G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --tool=memcheck

Bug#802306: packagekitd eating up RAM

On Sat, Dec 19, 2015, Stephen Kitt wrote: > Dear Maintainer, > > I'm also seeing excessive RAM use; packagekitd is currently using > 4.8GB of RAM (on my 32GB system). I’m tempted to suggest raising the severity of this bug. It has become unbearable, the insane memory usage of packagekitd

Bug#802306: packagekitd eating up RAM

On Tue, Jan 05, 2016, Matthias Klumpp wrote: > Hmm, are you doing anything special with PK which could trigger this > issue, so I can reproduce it? No, I’m afraid that’s the strange thing, I don’t do anything with PK. I run a GNOME desktop but have never launched software or performed any

Bug#802306: packagekitd eating up RAM

Hmm, are you doing anything special with PK which could trigger this issue, so I can reproduce it? PK itself should terminate after idling for a while, freeing any resources it still uses. In order to debug a potential memory leak, I would first need to be able to reproduce it... Cheers,

Bug#802306: packagekitd eating up RAM

On Tue, 5 Jan 2016 17:11:41 +0100, Matthias Klumpp wrote: > Hmm, are you doing anything special with PK which could trigger this > issue, so I can reproduce it? No, like Sam I'm just running Gnome, without even using gnome-software. > PK itself should terminate after

Bug#802306: packagekitd eating up RAM

Package: packagekit Version: 1.0.11-1 Followup-For: Bug #802306 Dear Maintainer, I'm also seeing excessive RAM use; packagekitd is currently using 4.8GB of RAM (on my 32GB system). Regards, Stephen -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500,

Bug#802306: packagekitd eating up RAM

Control: reassign -1 packagekit 1.0.10-1 On Lu, 19 oct 15, 09:24:01, Mike Gabriel wrote: > Package: packagekitd > Severity: important > Version: 1.0.10-1 > > Hi, > > on my Debian sid testing I have been observing high memory consumptions for > a while caused by packagekitd. > > I have to kill

Bug#802306: packagekitd eating up RAM

Package: packagekitd Severity: important Version: 1.0.10-1 Hi, on my Debian sid testing I have been observing high memory consumptions for a while caused by packagekitd. I have to kill packagekitd every once in a while, being a bit fed up with that now, I have removed it completely from