Dear Maintainer,

   * What led up to the situation?
     Upgrading gnome-shell on Debian/testing
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     apt -u dist-upgrade
   * What was the outcome of this action?
     gnome-shell process leaks memory on Debian/testing
   * What outcome did you expect instead?
     gnome-shell process not leaking memory

currently, since a while, the gnome-shell process leaks memory using gnome
shell with Wayland. I am using gnome-shell as Wayland process, and under
current Debian/testing environment, the process leaks memory and can get
several gigabyte large.

Output from 'top':

14237 adrian    20   0 9525320   1,3g 764448 S  15,9   8,6  35:33.41 gnome-
shell

As you can see in above example, the gnome-shell process uses 1,3GB random
access memory. Please bear in mind, that several gigabyte of memory usage are
already swapped out to the Linux swap partition.

% grep --color VmSwap /proc/14237/status
VmSwap:  2938064 kB

As in above example, ~3 gigabyte of memory are swapped out.

In conjunction with above recognition, the gnome shell (user interface)
'freezes' several seconds, from time to time.

Thank you very much for your kind attention,

Adrian Kieß

Dear Maintainer,

the bug in the gnome-shell process is still there in Debian/testing as
of the 2024-03-21.

The gnome-shell process leaks memory in a tremendous way. The process
can get up to 4-8 Gigabyte large.

Thank you for your kind attention.

Sincerely,

Adrian Kieß

Dear Maintainer of the gnome-shell package,

the bug I have described before, in that the gnome-shell process is
leaking memory, is fixed now.

Steps I followed and the bug is fixed:

* Disable the Open Weather temperature plugin for the Avtivities bar on
the top of the screen
* Upgrade all packages inside Debian/testing to the newest packages at
the 2024-05-02 and 2024-05-03 with apt -u dist-upgrade

The gnome-shell process stays now between 400MB and 450MB usage size in
random access memory.

Thank you very much for your kind attention.

Sincerely,

Adrian Kiess

Dear Maintainer,

I re-installed my Debian/testing installation completely new in the
mean-time, only taking serious old settings to the new Debian installation.

The problem/bug I described is gone.

Thank you.

Adrian