From: sirgazil via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 40116 <40116@debbugs.gnu.org>
Subject: bug#40116: GDM: Memory leak in .gnome-shell-real process
Date: Thu, 19 Mar 2020 13:13:32 -0500 [thread overview]
Message-ID: <170f4001961.121b1861f95704.959508865105831753@zoho.com> (raw)
In-Reply-To: 170ee024512.c9ac6ac476703.6325608537898017895@zoho.com
I tried a virtual machine with my system configuration during 4 hours and couldn't reproduce the leak (I used "guix system vm"). ".gnome-shell-real" kept using about 260 MiB of RAM and it actually went down to 220 at some point.
In 4 hours, in my real system, the leak would have been visible.
I'm planning to create another virtual machine with "guix system vm-image" instead to install all the packages I have in my user profile and leave it running overnight to see if there is any difference.
next prev parent reply other threads:[~2020-03-19 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:18 bug#40116: GDM: Memory leak in .gnome-shell-real process sirgazil via Bug reports for GNU Guix
2020-03-18 15:09 ` Ludovic Courtès
2020-03-18 16:10 ` sirgazil via Bug reports for GNU Guix
2020-03-29 16:08 ` Jan Nieuwenhuizen
2020-03-29 16:10 ` Jan Nieuwenhuizen
2020-03-18 16:09 ` Julien Lepiller
2020-03-19 18:13 ` sirgazil via Bug reports for GNU Guix [this message]
2020-03-22 0:38 ` sirgazil via Bug reports for GNU Guix
2020-03-23 17:01 ` sirgazil via Bug reports for GNU Guix
2020-03-24 13:15 ` sirgazil via Bug reports for GNU Guix
2020-10-01 15:56 ` Luis Felipe via Bug reports for GNU Guix
2022-03-23 11:35 ` bug#41215: memory leak in gnome-shell zimoun
2022-03-23 15:13 ` Luis Felipe via Bug reports for GNU Guix
2022-03-23 15:46 ` bug#40116: " zimoun
2022-03-23 16:00 ` Julien Lepiller
2022-04-09 15:19 ` bug#40116: GDM: Memory leak in .gnome-shell-real process Luis Felipe 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=170f4001961.121b1861f95704.959508865105831753@zoho.com \
--to=bug-guix@gnu.org \
--cc=40116@debbugs.gnu.org \
--cc=sirgazil@zoho.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.