[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [plasmashell] [Bug 387341] Memory leak in plasma shell with 5.10.5
From:       Alexander Schlarb <bugzilla_noreply () kde ! org>
Date:       2017-12-04 19:26:40
Message-ID: bug-387341-17878-9hLbScK7CC () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=387341

--- Comment #9 from Alexander Schlarb <alexander-kde@ninetailed.ninja> ---
@David Edmundson: Are you sure that this is a duplicate of 387128? Because from
what I can tell they have hardly anything to do with each other (afaik: one is
a memory leak caused by a buggy QML script buffering notifications, the other
is a bug in the Qt SceneGraph or the QML/QtQuick2 libraries as used by
PlasmaShell).

I have seen no evidence at this point to suggest that this issues may be
related aside from the leak happening "with QML" – but then almost everything
in PlasmaShell is QML in one why or another. The memory increases caused the
notification bug are one-time (per notification) events, while this bug is
about a slow, but continuous and (apparently) exponentional leak of memory. I'm
sorry if I didn't make this clear in my last comment.

On another note: Could you arrange for somebody with the nVidia binary driver
see if they can reproduce this issue? I feel it may stem from a specific
interaction between Qt and Mesa.

Recap on how to test for this:

 * Make sure you have plasma-desktop 5.10+ and Qt5 5.9.2
 * Start `plasmashell`
 * Add the "Media-Frame" Plasmoid to the desktop and select some folder with
pictures to display
 * Wait 5 to 10 minutes while regularily checking Plasma's memory usage and the
remaining "Available" system memory using `free`
 * If memory usage stablizes after the inital take-in, then you're not
affected, if it starts growing quickly (and continues to grow even after you
remove the Media-Frame) then you are affected

Hopefully that makes it clearer what this bug is and isn't about. (The above
also works if you don't receive a single notification during the entire
process.)

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]