Tested with chrome making the login on X website with my credentials saved,
gnome-keyring memory rose , logout and login on the same X website keyring
memory rose again... by the end of the week gnome-keyring is using almost 200mb
: O
(a lot of sites and ecomerce have timed logins so it
@wyderkat: which gnome-keyring version is that? There were *lots* of
leak fixes in 3.16 release.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
Another way to reproduce that bug:
ssh-keygen -t rsa -N "" -f ~/.ssh/newkey
ssh-copy-id -i ~/.ssh/newkey.pub localhost
while true; do ssh localhost date; done
Then sit and observe in another terminal how memory disappears.
--
You received this bug notification because you are a member of
This bug was fixed in the package gnome-keyring - 3.2.2-2ubuntu4.1
---
gnome-keyring (3.2.2-2ubuntu4.1) precise; urgency=low
* debian/patches/git_leak_fix.patch: rpc-layer: Fix memory leak in call
state pool, thanks Brian J. Murrell for pointing it (lp: #1094496)
-- Sebastien
I've finally been able to test the new version on both my home machine
and the work machine that originally showed the problem. Results seem
positive: memory usage appears normal and doesn't grow after a full day
of running.
directly after starting:
zelle24481 0.1 0.0 216800 4304 ?
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
gnome-keyring-daemon leaks memory
Status in
Hello Hein,
Were you able to test this in your reproducable environment yet?
Thanks!
Adam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
gnome-keyring-daemon
Hein, have you had a chance to test this at work?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
gnome-keyring-daemon leaks memory
Status in GNOME keyring
Dear Steve Langasek,
Brian, can you confirm that the SRUed version fixes the problem for you?
We need some confirmation of the bugfix before it can be published to
precise-updates.
As Seb pointed out earlier, this problem is not reproducible for all
users. By that measure, the test case
Brian, can you confirm that the SRUed version fixes the problem for you?
We need some confirmation of the bugfix before it can be published to
precise-updates.
As Seb pointed out earlier, this problem is not reproducible for all
users. By that measure, the test case in the bug description is
Hello Brian, or anyone else affected,
Accepted gnome-keyring into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/gnome-
keyring/3.2.2-2ubuntu4.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/precise-proposed/gnome-keyring
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
gnome-keyring-daemon leaks memory
Status in GNOME
The patch is applied in gnome-keyring = 3.6.1, so marking as Fix
Released. If you want to get this applied in previous releases, please
follow instructions at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.
** Changed in: gnome-keyring (Ubuntu)
Status: New = Fix Released
--
You
On 13-03-08 08:08 AM, Dmitry Shachnev wrote:
The patch is applied in gnome-keyring = 3.6.1,
Will that release go into the current LTS, 12.04? LTS is Long Term
Support so I would expect it to see bug fixes without requiring
individuals to file specific requests to have a bug fixed in it.
--
I don't have a 12.04 machine to build/test the fix on, maybe someone
else can do that.
Or you can apply the patch yourself and submit a merge proposal against
lp:ubuntu/precise/gnome-keyring, so that it'll show up in the
sponsorship queue. See
But I do have a 12.04 machine and I already submitted a patch (which
just came from upstream, not my patch) which fixes the problem on the
gnome-keyring shipped in 12.04 LTS. So really, I don't know why you are
proposing all of this rigmarole with backporting patches from g-k-r
3.6.1 and
It's all of this beauraucratic red-tape to getting such a simple but
important fix into what is supposed to be a supported release that makes
Ubuntu no longer a desired platform to use.
oh come on, what all of this beauraucratic red-tape, bugs just need basic
infos on
- impact (what's the
@Brian: I will SRU that fix, I've marked it on my todolist for a while,
but there is only so many hours in a week and only so many developers to
maintain some thousands packages accross several release of Ubuntu, such
comments don't make me feel motivated to do the work though :-(
--
You
** Also affects: gnome-keyring (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Title:
gnome-keyring-daemon
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-keyring (Ubuntu Precise)
Importance: Undecided = High
** Changed in: gnome-keyring (Ubuntu Precise)
Status: New = In Progress
** Description changed:
- gnome-keyring-daemon gets killed here
uploaded to the precise review queue:
http://launchpadlibrarian.net/133350726/gnome-
keyring_3.2.2-2ubuntu4.1_source.changes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1094496
Thanks Brian, do you have details on how to trigger the leak? It's not
happening to every user and to reach that usage you probably have a
client doing lot of keyring calls? I wonder if we could get a testcase
and a improve the testsuit once the bug fixed to make sure the issue
doesn't come back
On 13-01-07 01:06 PM, Sebastien Bacher wrote:
Thanks Brian, do you have details on how to trigger the leak?
Nothing more specific than just sit back and wait. :-) Seriously, I
don't to anything special here. I keep SSH and PGP keys in my keyring
and ssh a lot and sign every outgoing e-mail.
This patch from upstream bug #684351 seems to fix the problem here for
me.
** Patch added: patch to fix memory leak
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1094496/+attachment/3474829/+files/10_bz_684351_memory_leak.patch
** Bug watch added: GNOME Bug Tracker #684351
** Changed in: gnome-keyring
Status: Unknown = Fix Released
** Changed in: gnome-keyring
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
The attachment patch to fix memory leak of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
26 matches
Mail list logo
