From: sirgazil <sirgazil@zoho.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36100 <36100@debbugs.gnu.org>
Subject: bug#36100: Jami leaks memory
Date: Wed, 12 Jun 2019 17:15:13 -0500 [thread overview]
Message-ID: <16b4dc2633c.11b1e783627802.2566747870323318895@zoho.com> (raw)
In-Reply-To: <87zhmmsfi1.fsf@gnu.org>
---- On Wed, 12 Jun 2019 15:41:42 -0500 Ludovic Courtès <ludo@gnu.org> wrote ----
> sirgazil <sirgazil@zoho.com> skribis:
>
> > ---- On Wed, 12 Jun 2019 07:15:36 -0500 Ludovic Courtès <ludo@gnu.org> wrote ----
> >
> > > Hi sirgazil,
> > >
> > > sirgazil <sirgazil@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.
next prev parent reply other threads:[~2019-06-12 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 14:08 bug#36100: Jami leaks memory sirgazil
2019-06-12 12:15 ` Ludovic Courtès
2019-06-12 17:20 ` sirgazil
2019-06-12 20:41 ` Ludovic Courtès
2019-06-12 22:15 ` sirgazil [this message]
2019-06-13 7:30 ` Ludovic Courtès
2020-09-27 19:43 ` sirgazil via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16b4dc2633c.11b1e783627802.2566747870323318895@zoho.com \
--to=sirgazil@zoho.com \
--cc=36100@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).