GNU bug report logs -
#36100
Jami leaks memory
Previous Next
Reported by: sirgazil <sirgazil <at> zoho.com>
Date: Wed, 5 Jun 2019 14:04:02 UTC
Severity: normal
Done: sirgazil <sirgazil <at> zoho.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 36100 in the body.
You can then email your comments to 36100 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#36100
; Package
guix
.
(Wed, 05 Jun 2019 14:04:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
sirgazil <sirgazil <at> zoho.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 05 Jun 2019 14:04:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
When I run Jami in the GNU system installed with Guix, I see that its process called ".gnome-ring-rea" starts using around 36 MiB, but then increases over time at slow pace. After some hours, I notice it reaches 1 GiB of memory usage. I have to finalize the process to release memory.
This happens even when you are not doing anything in the application.
## Steps to reproduce (using GNOME)
1. $ guix install jami-client-gnome
2. Press Alt+F2 and run "ring.cx"
[2.1 Create a Jami account]
3. Press Alt+F2 and run "gnome-system-monitor"
4. Click on "Processes"
5. Locate the ".gnome-ring-rea" process
6. Observe the "Memory" usage for a few hours
I don't know if step 2.1 is necessary, but I already had an account created when I noticed the problem for the first time.
## System information
```
$ guix describe
Generation 2 May 20 2019 10:23:06 (current)
guix 0655c16
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 0655c16e7561cffe2fe26bd9b24af1a0efc2c859
```
---
https://sirgazil.bitbucket.io/
Information forwarded
to
bug-guix <at> gnu.org
:
bug#36100
; Package
guix
.
(Wed, 12 Jun 2019 12:16:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 36100 <at> debbugs.gnu.org (full text, mbox):
Hi sirgazil,
sirgazil <sirgazil <at> zoho.com> skribis:
> When I run Jami in the GNU system installed with Guix, I see that its process called ".gnome-ring-rea" starts using around 36 MiB, but then increases over time at slow pace. After some hours, I notice it reaches 1 GiB of memory usage. I have to finalize the process to release memory.
Do you think it’s a Guix-specific issue?
I would expect it to not be Guix-specific. Could you report the issue
upstream?
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#36100
; Package
guix
.
(Wed, 12 Jun 2019 17:21:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 36100 <at> debbugs.gnu.org (full text, mbox):
---- On Wed, 12 Jun 2019 07:15:36 -0500 Ludovic Courtès <ludo <at> gnu.org> wrote ----
> Hi sirgazil,
>
> sirgazil <sirgazil <at> zoho.com> skribis:
>
> > When I run Jami in the GNU system installed with Guix, I see that its process called ".gnome-ring-rea" starts using around 36 MiB, but then increases over time at slow pace. After some hours, I notice it reaches 1 GiB of memory usage. I have to finalize the process to release memory.
>
> Do you think it’s a Guix-specific issue?
>
> I would expect it to not be Guix-specific. Could you report the issue
> upstream?
Oh, I think one of my messages about this issue didn't arrived. The leak in the version available in Guix is known and fixed upstream.
I thought that maybe this bug report could be used as a reminder to update the package definition of Jami in Guix to a version that fixes the leak?
Information forwarded
to
bug-guix <at> gnu.org
:
bug#36100
; Package
guix
.
(Wed, 12 Jun 2019 20:42:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 36100 <at> debbugs.gnu.org (full text, mbox):
sirgazil <sirgazil <at> zoho.com> skribis:
> ---- On Wed, 12 Jun 2019 07:15:36 -0500 Ludovic Courtès <ludo <at> gnu.org> wrote ----
>
> > Hi sirgazil,
> >
> > sirgazil <sirgazil <at> zoho.com> skribis:
> >
> > > When I run Jami in the GNU system installed with Guix, I see that its process called ".gnome-ring-rea" starts using around 36 MiB, but then increases over time at slow pace. After some hours, I notice it reaches 1 GiB of memory usage. I have to finalize the process to release memory.
> >
> > Do you think it’s a Guix-specific issue?
> >
> > I would expect it to not be Guix-specific. Could you report the issue
> > upstream?
>
>
> Oh, I think one of my messages about this issue didn't arrived. The leak in the version available in Guix is known and fixed upstream.
Nice. Should we apply their patch, or upgrade our package?
> I thought that maybe this bug report could be used as a reminder to update the package definition of Jami in Guix to a version that fixes the leak?
I think it’s better if the bug report is actionable.
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#36100
; Package
guix
.
(Wed, 12 Jun 2019 22:16:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 36100 <at> debbugs.gnu.org (full text, mbox):
---- On Wed, 12 Jun 2019 15:41:42 -0500 Ludovic Courtès <ludo <at> gnu.org> wrote ----
> sirgazil <sirgazil <at> zoho.com> skribis:
>
> > ---- On Wed, 12 Jun 2019 07:15:36 -0500 Ludovic Courtès <ludo <at> gnu.org> wrote ----
> >
> > > Hi sirgazil,
> > >
> > > sirgazil <sirgazil <at> zoho.com> skribis:
> > >
> > > > When I run Jami in the GNU system installed with Guix, I see that its process called ".gnome-ring-rea" starts using around 36 MiB, but then increases over time at slow pace. After some hours, I notice it reaches 1 GiB of memory usage. I have to finalize the process to release memory.
> > >
> > > Do you think it’s a Guix-specific issue?
> > >
> > > I would expect it to not be Guix-specific. Could you report the issue
> > > upstream?
> >
> >
> > Oh, I think one of my messages about this issue didn't arrived. The leak in the version available in Guix is known and fixed upstream.
>
> Nice. Should we apply their patch, or upgrade our package?
Hmm, I'm really ignorant about what would be best. As a desktop user, I think anything that allows me to install and use Jami without leaks.
> > I thought that maybe this bug report could be used as a reminder to update the package definition of Jami in Guix to a version that fixes the leak?
>
> I think it’s better if the bug report is actionable.
Sorry, Ludo, I don't understand what actionable means in this context.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#36100
; Package
guix
.
(Thu, 13 Jun 2019 07:31:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 36100 <at> debbugs.gnu.org (full text, mbox):
Hi sirgazil,
sirgazil <sirgazil <at> zoho.com> skribis:
> > > I thought that maybe this bug report could be used as a reminder to update the package definition of Jami in Guix to a version that fixes the leak?
> >
> > I think it’s better if the bug report is actionable.
>
>
> Sorry, Ludo, I don't understand what actionable means in this context.
What I mean is that the bug should highlight something we, Guix people,
can do about it. If it were reporting a purely upstream issue, there’s
little we can do on our side, apart from upgrading or applying fixes
available upstream.
I hope that makes sense!
Thanks,
Ludo’.
Reply sent
to
sirgazil <sirgazil <at> zoho.com>
:
You have taken responsibility.
(Sun, 27 Sep 2020 19:44:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
sirgazil <sirgazil <at> zoho.com>
:
bug acknowledged by developer.
(Sun, 27 Sep 2020 19:44:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 36100-done <at> debbugs.gnu.org (full text, mbox):
I'm closing this issue because the package the report was filed against was removed from Guix:
gnu: jami-client-gnome: Remove deprecated package.
commit 8551bc64e4322080ef07b5009f4d46229df8d6f3
Date: Sun Jul 12 18:00:46 2020 +0200
Also, there is a new package for Jami that I tried out:
Guix System 97e98e2
Jami 20200710.1.6bd18d2
I followed the steps below to try reproduce the issue with this new version and I could not see any memory leak.
1. $ guix install jami
2. Press Alt+F2 and run "jami"
2.1. Create a Jami account
3. Press Alt+F2 and run "gnome-system-monitor"
4. Click on "Processes"
5. Locate the "jami" process
6. Observe the "Memory" use for a few hours
Problem solved.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 26 Oct 2020 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 180 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.