From: Julien Lepiller <julien@lepiller.eu>
To: sirgazil <sirgazil@zoho.com>, 40116@debbugs.gnu.org
Subject: bug#40116: GDM: Memory leak in .gnome-shell-real process
Date: Wed, 18 Mar 2020 12:09:36 -0400 [thread overview]
Message-ID: <4F9A8305-EA95-44E5-825D-F0C9FB5B1705@lepiller.eu> (raw)
In-Reply-To: <170ee024512.c9ac6ac476703.6325608537898017895@zoho.com>
Le 18 mars 2020 10:18:11 GMT-04:00, sirgazil via Bug reports for GNU Guix <bug-guix@gnu.org> a écrit :
>I can't use GNOME anymore because of the problem I explained in the
>following thread:
>
>https://lists.gnu.org/archive/html/help-guix/2020-02/msg00206.html
>
>On recent system upgrades, the problem got worse. Before, I could get
>to the end of the day despite the leak; but now it takes around 3 hours
>for the .gnome-shell-real process run by the gdm user to eat the
>remaining RAM.
>
>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).
>
>My current guix:
>
>$ guix describe
>Generation 61 Mar 15 2020 08:44:39 (current)
> sirgazil-x 8274cd7
> repository URL: https://gitlab.com/sirgazil/guix-channel-x.git
> branch: master
> commit: 8274cd78f9f6d58e00e057a0eabe58e4e143cc4d
> guix a431a63
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: a431a63537c8103b2a58c9a55d90184fb5c90361
>
>
>---
>https://sirgazil.bitbucket.io/
I'm also hit by that bug. I do not use gnome though, and the .gnome-session-real process is owned by gdm. Ram usage is at around 200MB when starting and after a few days (putting the laptop to sleep during the night), it got to 2.4GB, even though I don't really need or use it beside logging in. After another restart, it was at 600MB after a day. That memory usage is ridiculous :/
next prev parent reply other threads:[~2020-03-18 16:10 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 [this message]
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=4F9A8305-EA95-44E5-825D-F0C9FB5B1705@lepiller.eu \
--to=julien@lepiller.eu \
--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 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).