cmpilato,
To avoid confusing symptoms between various peoples' machines please
open your own bug by running:
ubuntu-bug gnome-shell
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I meant to say, "I have *no* extensions installed that don't..."
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1850201
Title:
Memory usage grows when locking/unlocking the
I'm also seeing a steady growth in gnome-shell's memory usage over time. I
have extensions installed that don't appear to be required by Ubuntu 20.04
(meaning if I try to 'apt remove'
them, apt wants to remove 'ubuntu-deskop', too).
Here's the listing of my relevant extensions directories:
$
** Tags removed: leak
** Tags added: gnome-shell-leak
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1850201
Title:
Memory usage grows when locking/unlocking the screen
To
** Bug watch removed: gitlab.gnome.org/GNOME/gjs/issues #217
https://gitlab.gnome.org/GNOME/gjs/issues/217
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/issues #1886
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886
--
You received this bug notification because you are a
Which extensions would you consider the default Ubuntu ones?
I'm not finding memory usage lower in 20.04 -- I was at over 1.4G RSS
earlier today before I rebooted.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
Please also remember to keep all extensions uninstalled while
investigating leaks. We don't want to spend time finding leaks in
extensions unless they happen to be the default Ubuntu ones.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
It would be hard to prove that's a bug at all, or just the natural
resident set size that the gnome-shell process settles at until the next
garbage collection. And you can't predict or know when that will happen.
Generally speaking for gnome-shell I would say anything under 500MB
might not be a
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1850201
Title:
Memory usage grows when locking/unlocking the screen
To manage notifications about this bug
In Ubuntu 20.04 (with the newest packages) the leak is present. After
logging in the memory usage of gnome-shell is 208MB. After pushing
Super+A it jumps to 213MB and stay there. After lock/unlock the screen
it jumps to 270MB and stays there. Repeated Super+A and lock/unlock
seems to do no further
** Tags added: leak
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1850201
Title:
Memory usage grows when locking/unlocking the screen
To manage notifications about this bug
No, gnome-shell#1886 is being tracked in Launchpad bug 1856838 already,
which is more appropriate than here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1850201
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Description changed:
- Many times after logging in gnome-shell uses 600-800kB of memory, and
+ Many times after logging in gnome-shell uses 600-800MB of memory, and
also slows down quite a bit (e.g., 20-30 seconds waiting for login).
Only after multiple resets (Alt+F2 r) drops the memory
Here is a similar issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1886
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I'm trying to catch that function(s) which leaks the memory, but
unfortunately I am not an expert. Can anyone help me what to do? I
copied /usr/bin/gnome-shell to /usr/bin/gnome-shell.bin and made a
script in /usr/bin/gnome-shell:
#!/bin/sh
if [ $USER = gstest ] ; then exec valgrind --tool=massif
What does it mean "doesn't free memory immediately"? Hours? Days? I never
experienced decrease in memory usage, except for small fluctuations. I think it
is a memory leak added to this slow garbage collection.
I also wrote about this problem to
https://gitlab.gnome.org/GNOME/gjs/issues/217# but
gnome-shell (via gjs and mozjs) actually doesn't free memory immediately
when JavaScript objects get deleted. It defers the garbage collection
until more stress (more memory use) is put on the system.
What this means is even without any leaks it will appear to grow for
some period of time before
The main system which I use for work is Ubuntu 18.04.3 LTS. I use gnome with
many extensions (see above). At the beginning the memory usage of gnome-shell
is ~177MB. (Interesting that in another machine, which is a laptop and has
exactly the same system and almost the same hardware, gnome-shell
Yes, MB, not kB.
Today I made a new test. I logged in (ubuntu 19.10 on virtualbox, normal ubuntu
session) and started the gnome-system-monitor to see what is happening. The
memory usage of gnome-shell was ~202MB at the beginning. I locked the session,
and unlocked it. The memory usage jumped to
20 matches
Mail list logo
