From: sirgazil via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40116 <40116@debbugs.gnu.org>
Subject: bug#40116: GDM: Memory leak in .gnome-shell-real process
Date: Wed, 18 Mar 2020 11:10:49 -0500 [thread overview]
Message-ID: <170ee6964e3.ee395bf578532.436612750827795239@zoho.com> (raw)
In-Reply-To: <87a74d8zsq.fsf@gnu.org>
---- On Wed, 18 Mar 2020 10:09:57 -0500 Ludovic Courtès <ludo@gnu.org> wrote ----
[...]
> > It seems that the bug is stronger in the GNOME desktop, but I've seen, at least once, .gnome-shell-real using an abnormal amount of RAM while in sway (about 800 MiB).
>
> Could you check if it happens in a VM? That is, you build your GNOME
> config with ‘guix system vm’, try to do some activity in the VM, and
> check in top whether ‘gnome-shell’ is growing.
I can try, but last time I did something like that the VM with GNOME was too slow to do anything (this computer only has 4 GiB of RAM).
next prev parent reply other threads:[~2020-03-18 16:12 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 [this message]
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
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
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=170ee6964e3.ee395bf578532.436612750827795239@zoho.com \
--to=bug-guix@gnu.org \
--cc=40116@debbugs.gnu.org \
--cc=ludo@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 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).