From: sirgazil <sirgazil@zoho.com>
To: sirgazil <sirgazil@zoho.com>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: GDM, GNOME and RAM issue
Date: Tue, 25 Feb 2020 11:00:07 -0500 [thread overview]
Message-ID: <1707d13b24e.1116d4da766662.6906684847757146967@zoho.com> (raw)
In-Reply-To: <17078361cfc.cd3808e751818.4275702550541103094@zoho.com>
---- On Mon, 24 Feb 2020 12:19:37 -0500 sirgazil <sirgazil@zoho.com> wrote ----
> Hello,
>
> I've been experiencing the following behavior for months, but didn't have the time to report anything.
>
> When I boot, a fresh GNOME session uses around 1.3 GiB (I don't know if this is normal).
>
> After several hours of work, the desktop starts feeling somewhat slow (e.g. when launching apps, switching work spaces). When this happens, RAM usage is around 3 GiB (of 4 GiB in total). If I continue working, RAM usage continues to go up little by little, and I have to reboot at some point, because memory is not released and things become slower.
Actually, I left the computer on overnight and this morning it was so slow that the cursor barely moved. So it seems it doesn't matter whether I do any interaction with the running applications, RAM usage grows anyways.
Resources in GNOME System Control:
https://multimedialib.files.wordpress.com/2020/02/gnome-ram-eaten-resources-2020-02-25.png
Processes in GNOME System Control:
https://multimedialib.files.wordpress.com/2020/02/gnome-ram-eaten-processes-2020-02-25.png
Processes in top:
https://multimedialib.files.wordpress.com/2020/02/gnome-ram-eaten-top-2020-02-25.png
Again, the ".gnome-shell-real" run by the gdm user seems to be the problem.
next prev parent reply other threads:[~2020-02-25 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 17:19 GDM, GNOME and RAM issue sirgazil
2020-02-25 16:00 ` sirgazil [this message]
2020-03-18 14:31 ` sirgazil
2020-03-18 17:10 ` Catonano
2020-03-19 13:55 ` sirgazil
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=1707d13b24e.1116d4da766662.6906684847757146967@zoho.com \
--to=sirgazil@zoho.com \
--cc=help-guix@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.
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).