[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Flöser]

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

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #10 from Martin Flöser  ---
Should be fixed in 5.10.4. At least I found a bug in Aurorae which made the
session unusable (did not look at memory consumption but it recursively created
OpenGL contexts, so yes quite likely memory increase) and fixed it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 CC||yy...@gmx.com

--- Comment #9 from Christoph Feck  ---
*** Bug 379735 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Component|wayland-generic |aurorae

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Jaime Torres]

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

--- Comment #8 from Jaime Torres  ---
Confirmed, with breeze ("brisa"), kwin_wayland works perfectly fine.

You can close this bug, unless you think we should wait until the patch you
mentioned is available in Tumbleweed, because I don't have a development
environment in the laptop to test the master branch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

--- Comment #7 from Martin Gräßlin  ---
Just had a look into massif and it seems to confirm that it is related to
aurorae. There is one element of 677 MiB and it is from inside Aurorae. It
might be possible that ac08c5ac9d4532b2506c76e8b69249b32d365aa3 fixed this
issue, too. But that's only in master

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

--- Comment #6 from Martin Gräßlin  ---
Given the debug output it could be related to the window decoration you are
using. I haven't tested aurorae much on Wayland, consider giving a try to the
default breeze.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Jaime Torres]

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

--- Comment #5 from Jaime Torres  ---
Created attachment 105259
  --> https://bugs.kde.org/attachment.cgi?id=105259=edit
the other massif output

I have installed all the air* oxygen* plasma-* packages i have found, and the
messages are still there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Jaime Torres]

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

--- Comment #4 from Jaime Torres  ---
Created attachment 105258
  --> https://bugs.kde.org/attachment.cgi?id=105258=edit
one of the massif.output

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Jaime Torres]

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

--- Comment #3 from Jaime Torres  ---
There are also thousands of lines like the following in the stdout:

The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/maximize.svgz"
doesn't contain any of the prefixes ("pressed-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/maximize.svgz"
doesn't contain any of the prefixes ("deactivated")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/close.svgz"
doesn't contain any of the prefixes ("deactivated-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/close.svgz"
doesn't contain any of the prefixes ("pressed-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/close.svgz"
doesn't contain any of the prefixes ("deactivated")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/alldesktops.svgz" doesn't
contain any of the prefixes ("deactivated-inactive")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/alldesktops.svgz" doesn't
contain any of the prefixes ("pressed-inactive")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/alldesktops.svgz" doesn't
contain any of the prefixes ("deactivated")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/decoration.svgz" doesn't
contain any of the prefixes ("innerborder-inactive")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/decoration.svgz" doesn't
contain any of the prefixes ("decoration-maximized-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/restore.svgz"
doesn't contain any of the prefixes ("deactivated-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/restore.svgz"
doesn't contain any of the prefixes ("pressed-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/restore.svgz"
doesn't contain any of the prefixes ("deactivated")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/maximize.svgz"
doesn't contain any of the prefixes ("deactivated-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/maximize.svgz"
doesn't contain any of the prefixes ("pressed-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/maximize.svgz"
doesn't contain any of the prefixes ("deactivated")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/close.svgz"
doesn't contain any of the prefixes ("deactivated-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/close.svgz"
doesn't contain any of the prefixes ("pressed-inactive")
The image "/home/jtorres/.local/share/aurorae/themes/air-oxygen/close.svgz"
doesn't contain any of the prefixes ("deactivated")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/alldesktops.svgz" doesn't
contain any of the prefixes ("deactivated-inactive")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/alldesktops.svgz" doesn't
contain any of the prefixes ("pressed-inactive")
The image
"/home/jtorres/.local/share/aurorae/themes/air-oxygen/alldesktops.svgz" doesn't
contain any of the prefixes ("deactivated")

I'm going to check if I have air-oxygen installed and check again.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Jaime Torres]

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

--- Comment #2 from Jaime Torres  ---
Created attachment 105255
  --> https://bugs.kde.org/attachment.cgi?id=105255=edit
Valgrind output of a nested kwin_wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 379338] huge memory usage. from 0 to 16Gb in less than 30 seconds

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

   Severity|critical|major
  Flags||Wayland+, X11-
  Component|platform-wayland|wayland-generic

--- Comment #1 from Martin Gräßlin  ---
Can you try to only run a nested kwin_wayland in an X11 session and check
whether the problem happens there as well. If yes, that would allow to run
valgrind on it. If not we need to look for another solution. Investigating the
startup of the Plasma Wayland session is unfortunately not trivial.

I reduced the importance to major as currently we don't have critical bugs on
Wayland yet.

-- 
You are receiving this mail because:
You are watching all bug changes.