FS#60625 - mutter 3.30.1 introduced a new memory leak

Attached to Project: Arch Linux
Opened by Thiago (killown) - Sunday, 28 October 2018, 23:32 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 07 November 2018, 15:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

mutter 3.30.1 introduced a new memory leak

https://gitlab.gnome.org/GNOME/mutter/commit/8200995fdbf04b2763d33cd30d7c8174eebc1736
https://gitlab.gnome.org/GNOME/mutter/commit/71a62bb18fe3aebc6668bd37ef6917398ef71ae1

Additional info:
* package version mutter 3.30.1
* config and/or log files etc.


Steps to reproduce:
Memory leak.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 07 November 2018, 15:45 GMT
Reason for closing:  No response
Additional comments about closing:  Initial ticket would seem to be fixed
Comment by loqs (loqs) - Wednesday, 31 October 2018, 17:08 GMT
@killown can you confirm the issue is resolved in mutter 3.30.1+8+g1abab3fe2-1?
Comment by Thiago (killown) - Friday, 02 November 2018, 10:54 GMT
Still not resolved. gnome-shell process memory usage is increasing as time goes.
Comment by loqs (loqs) - Friday, 02 November 2018, 13:01 GMT
Please see https://gitlab.gnome.org/GNOME/mutter/commits/gnome-3-30 1abab3fe2 contains the two referenced commits.
Comment by Thiago (killown) - Friday, 02 November 2018, 22:36 GMT
Still not resolved. gnome-shell process memory usage is increasing as time goes.
Comment by Doug Newgard (Scimmia) - Sunday, 04 November 2018, 22:11 GMT
Posting the same thing doesn't help anyone. Either the problem is fixed with 3.30.1+8 or your initial post is wrong.

Loading...