memory leak in gnome-shell

  • Done
  • quality assurance status badge
Details
5 participants
  • Arne Babenhauserheide
  • Julien Lepiller
  • Leo Famulari
  • Luis Felipe
  • zimoun
Owner
unassigned
Submitted by
Arne Babenhauserheide
Severity
important
Merged with
A
A
Arne Babenhauserheide wrote on 12 May 2020 21:47
(address . bug-guix@gnu.org)
878shxndfi.fsf@web.de
I see a memory leak in Gnome Shell 3.32.2

The following is top output after several days of uptime:

PID USER PR NI VIRT RES %CPU %MEM ZEIT+ S BEFEHL
864 gdm 20 0 39,6g 1,1g 0,0 3,5 85:04.12 S /gnu/store/3r8h4lygzs06jyx89ffi1y2bbda9s76y-gnome-shell-3.32.2/bin/.gnome-shell-real

RES 1.1g is a bit much.

I tried to capture a coredump with gcore -o /tmp/gnome-shell 864, but
that increased the memory usage to 8g RES before I killed gcore.

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
L
L
Leo Famulari wrote on 15 May 2020 19:13
(no subject)
(address . control@debbugs.gnu.org)
20200515171354.GA25761@jasmine.lan
severity 41215 important
merge 41215 40116
Z
Z
zimoun wrote on 23 Mar 2022 12:35
Re: bug#41215: memory leak in gnome-shell
(name . sirgazil)(address . sirgazil@zoho.com)
86wngkzyss.fsf@gmail.com
Hi,

On Wed, 18 Mar 2020 at 09:18, sirgazil <sirgazil@zoho.com> wrote:

Toggle quote (2 lines)
> I can't use GNOME anymore because of the problem I explained in the following thread:

[...]

Toggle quote (3 lines)
> $ guix describe
> Generation 61 Mar 15 2020 08:44:39 (current)

What is the status of this old bug [1]? Especially since the last merge
of core-updates.




Cheers,
simon
L
L
Luis Felipe wrote on 23 Mar 2022 16:13
(name . zimoun)(address . zimon.toutoune@gmail.com)
Sw6_lvAJLpt_jWSh15ZkjfOfZuedhmMqPU4gKkruJWueFJ_m13ItHIviJcciGq5gM-4PO0sgVacvaMqmV3ZzJilqaXs_7QLdvMgH6gBsDec=@protonmail.com
Hi zimoun,

On Wednesday, March 23rd, 2022 at 11:35 AM, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (4 lines)
>

> What is the status of this old bug [1]? Especially since the last merge

At least on my side (I'm sirgazil), the status remains the same: this is not an issue anymore.

I didn't close the issue, though, because I wanted to hear from other people affected by it first.

So, if Julien and Arne, for example, don't experience the issue anymore, I'm happy to close the issue.
Attachment: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc
Attachment: signature.asc
Z
Z
zimoun wrote on 23 Mar 2022 16:46
(name . Luis Felipe)(address . luis.felipe.la@protonmail.com)
CAJ3okZ1_KNLF+Z_JNaQ9rQ14GTEE9cvhXZ_rvG77Jw-WuvXX0g@mail.gmail.com
Hi Luis,

On Wed, 23 Mar 2022 at 16:13, Luis Felipe <luis.felipe.la@protonmail.com> wrote:

Toggle quote (2 lines)
> So, if Julien and Arne, for example, don't experience the issue anymore, I'm happy to close the issue.

Let wait 15 days and if no answer, let assume it is not an issue and
close it. :-)

Thank you for your feedback.

Cheers,
simon
J
J
Julien Lepiller wrote on 23 Mar 2022 17:00
C4582435-0768-469F-8DB1-3F52B1B1D59F@lepiller.eu
On March 23, 2022 4:46:53 PM GMT+01:00, zimoun <zimon.toutoune@gmail.com> wrote:
Toggle quote (17 lines)
>Hi Luis,
>
>On Wed, 23 Mar 2022 at 16:13, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
>> So, if Julien and Arne, for example, don't experience the issue anymore, I'm happy to close the issue.
>
>Let wait 15 days and if no answer, let assume it is not an issue and
>close it. :-)
>
>Thank you for your feedback.
>
>Cheers,
>simon
>
>
>

I haven't had that issue in a while, I tgink we can close.
?
Your comment

This issue is archived.

To comment on this conversation send an email to 41215@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 41215
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch