[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Noah Davis]

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

Noah Davis  changed:

   What|Removed |Added

 CC||noaha...@gmail.com
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #36 from Noah Davis  ---
Regardless of where it was fixed, this appears to be fixed. I cannot reproduce
the bug with Qt 5.15, Breeze 5.19.80 or Kate 20.07.70.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #35 from Anthony  ---
It's Qt issue in setPalette, i can confirm it on radeon oss and intel. Still
present but since palettehelper is removed it has leak only when new colors are
applied. It can be closed since it's not KDE related.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Martin Gräßlin via KDE Bugzilla]

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

Martin Gräßlin  changed:

   What|Removed |Added

 CC||mgraess...@kde.org
   Severity|critical|normal

--- Comment #34 from Martin Gräßlin  ---
No new replies since March - I assume this issue is fixed and not critical any
more?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[cpon via KDE Bugzilla]

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

cpon  changed:

   What|Removed |Added

 CC||cpigat...@gmail.com

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #33 from Anthony  ---
Present in Qt 5.6 setPalette or radeon oss specific issue ?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #32 from Hugo Pereira Da Costa  ---
Hi Kai,
Thanks ! thats useful.
Now oxygen and breeze share a lot of code. Would be nice if you could do the
same test with ... plastique. This is a 'pure QT4' widget theme, so that it
would at least put me completely off the hook.

Thanks in advance,

Hugo

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Kai Uwe Broulik via KDE Bugzilla]

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

--- Comment #31 from Kai Uwe Broulik  ---
I now ran for a couple of hours with Oxygen and I already have 1,6 GiB of RAM
usage for X and this is Plasma 4.x, so I'm not sure this is an issue on our
side?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #30 from Anthony  ---
I make a review https://git.reviewboard.kde.org/r/127204/
The leak is in [QApplication/QGuiApplication] setPalette, how to fix in Qt i
have no idea.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #29 from Hugo Pereira Da Costa  ---
Hi Kai, Anthony
Sorry to say, but this bug report is a mess.
- First the original title is too generic and the actual problem is referred to
is _fixed_
- second, other issues (with the same symptom - large X memory-, but different
trigger conditions (change of color palette, change of widget theme, or - for
kai- nothing, just long uptime), have been appended, and I can't make anything
out of it. 
We need to clean this up;
1/ I will try reproduce the issue with switching coloscheme, widget style. But
please move this to a separater bug report. When doing so, please make the
title explicit enough, so that other unrelated issues do not get appended
there. 
2/ kai: unless this is related to the same modus opperandi as describe in the
first comment, this should also go to a separate bug report, also: related to
the Qt4 variant. Also would be nice to know if you have the same issue with
other widgets themes (oxygen, plastique, etc.)
Could well be simply a driver issue (leaks in X are quite often this, sadly.
For instance, in the past we have had huge issues with oxygen and nvidia
proprietary drivers).

3) then, when the "new things" are moved to their right place, we can _again_
close this bug report (which _is_ fixed, as far as I can tell). And I can
happily focus on the new ones.

Best,

Hugo

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Kai Uwe Broulik via KDE Bugzilla]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||k...@privat.broulik.de

--- Comment #28 from Kai Uwe Broulik  ---
Since I switched to an AMD GPU with the Radeon driver I also get huge RAM
consumption of X, after two days of uptime (leaving the machine on over night)
it consumes 5 GB! Note that this is a Plasma 4 machine but I am using the
Breeze widget theme (Qt 4 variant) there too.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #27 from Anthony  ---
To make new bug request for color settings
systemsettings5 -> color -> apply color scheme (no matter what) Xorg ram *2

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #26 from Anthony  ---
If Breeze set color scheme i can notice color setting cause a leak *2 ram seems
bug in color palette?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[David Edmundson via KDE Bugzilla]

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

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk

--- Comment #24 from David Edmundson  ---
Anthony, so what's the current status? 
You said it doesn't leak, then said it does.

Do you have a trace of this leak?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #25 from Anthony  ---
X leaks are difficult to trace, if you know easy way :) Yes, leak still present
only on applying breeze style in systemsettings. First apply Oxygen or other
then apply breeze Xorg Ram usage *2. Same branch 5.5 and master has same leak.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

Anthony  changed:

   What|Removed |Added

 Resolution|REMIND  |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #23 from Anthony  ---
Master has same leaks on applying application style.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

Anthony  changed:

   What|Removed |Added

 Resolution|WONTFIX |REMIND

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

Anthony  changed:

   What|Removed |Added

 Resolution|FIXED   |WONTFIX

--- Comment #22 from Anthony  ---
I notice more leaks. Master WORKS without leaks.
1. Apply other style except breeze in Application style
2. Apply breeze in Application style
3. Leaks on X, not so aggressive, but make usage *2

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Rex Dieter via KDE Bugzilla]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #13 from Anthony  ---
What is more "easy" to see
diff between 5.4.3 with 5.4.90
or 5.5.3 with master?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #16 from Hugo Pereira Da Costa  ---
Thanks ! That helps. 
Apologies, for not catching that up before.
I "think" I might know where the issue come from then. If I post a patch here
(to breeze only), would you be ok to test it on top of 5.5.3, before I backport
? 
Otherwise, I can try backport blindly.

Hugo

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #11 from Anthony  ---
Arch Linux - Qt 5.5.1 xcb 1.11.1 kf 5.18 Xorg 1.18
KaOS - Qt 5.5.1 xcb 1.11.1 kf 5.18 Xorg 1.17.4
Rosa Linux - Qt 5.5.1 xcb 1.9.1 kf 5.17 Xorg 1.15.2
Same hardware - e350 radeon (oss) what else?
No issue from 5.1.1 to 5.4.90 and with master, issues with all 5.4.90 to 5.5.3
only with Breeze.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #17 from Anthony  ---
I will test it.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #10 from Hugo Pereira Da Costa  ---
Hi, 

I never doubted that the problem you report is true, nor did I say anywhere
that I did not believe you.
I merely stated that on my machine, I cannot reproduce this issue, this whether
I use the latest version of breeze, or the same as you. Now there can be many
reasons for this discrepancy. Qt version, X version, graphics card driver,
upstream frameworks version, and what not. 
But whatever the reason, without further help on your side, there is no way I
can fix this bug myself, since I do not see it (on the only machine I have). 
In order to move forward I have no choice but wait either for your help, or for
the help from someone else who is experiencing the same problem as you. 
In the meanwhile and if you cannot provide the help I need (for whatever
reason), and if you still want a usable machine, I'll recommend to switch to
oxygen or fusion, or whatever. 

Best regards,

Hugo

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #12 from Hugo Pereira Da Costa  ---
Thanks for the info.
So, for Qt, I have same as you, for kf5 I have master, xcb, 1.10 and Xorg 1.14
Graphics card, intel.
Cannot upgrade xcb and Xorg, change hardware, and cannot downgrade kf5 easily.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #18 from Hugo Pereira Da Costa  ---
Created attachment 96588
  --> https://bugs.kde.org/attachment.cgi?id=96588=edit
possible patch

Here you go.
Thanks for testing and reporting back. 
Make sure to keep a copy of the code (either manually or via git), before
applying the patch because it is somewhat invasive (for breeze)
I have tested that the code compiles and runs fine though, after applying the
patch on top of 5.5.3, so it should at least 'not be worse' than what you have
now.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #15 from Anthony  ---
Yes, master has no leak at all. Only branch 5.5 is affected.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #19 from Anthony  ---
Yes, patch works, no leaks. Why master is about 10MB smaller, if can remove
more uneeded code, i will test :)

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

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

--- Comment #20 from Hugo Pereira Da Costa  ---
(In reply to Anthony from comment #19)
> Why master is about 10MB smaller, if can remove
> more uneeded code, i will test :)
No clue. But better not fix something that is not broken.
Anyway, thanks for helping on this.
I have backported all the changes corresponding to the patch you tested to
Plasma/5.5 so that the next release (5.5.4) should be alright.
Closing as fixed.

best,

Hugo

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #3 from Hugo Pereira Da Costa  ---
(though now I am only using Qt-5.5.1)

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #2 from Hugo Pereira Da Costa  ---
... or am I not looking at the right quantity ?

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #5 from Hugo Pereira Da Costa  ---
Thanks for the screenshots 
unfortunately no luck at reproducing still, with ksysguard, this using either
breeze from 5.5.3 (same as you) or breeze from master.
Note also that I would have no clue where breeze would allocate 250 Mb of data
of any kind per instance ... 
Could you try compiling breeze from "master" rather than the branch and reporte
if the issue persists ? there have been 'weird' issues at widget initialization
between 5.5.3 and master, which i could not all reproduce, but 'fixed' on the
machines where the problem occured, so it might be worth a try for you too.
Compiling breeze from source should not be too big a deal, but don't hesitate
to ask if you need how-to's.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #4 from Anthony  ---
Without leak -> http://oi63.tinypic.com/t4zajt.jpg
With leak -> http://oi64.tinypic.com/2h5mt4x.jpg
Huge is really HUGE > 500MB on 2 starts

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

Hugo Pereira Da Costa  changed:

   What|Removed |Added

 CC||hugo.pere...@free.fr

--- Comment #1 from Hugo Pereira Da Costa  ---
Hi,

Thanks for reporting.
But please quantify "huge"
I cannot reproduce here with the provided instructions:

top reports: 
before starting 10 kwrite
25800 root  20   0  279m  69m  44m S1  1.8   1:09.16 X  

after starting 10 kwrite
25800 root  20   0  357m 145m 120m S5  3.8   1:09.97 X  

after closing the 10 kwrite
25800 root  20   0  278m  69m  44m R4  1.8   1:10.85 X  

Hugo

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #6 from Anthony  ---
You cannot expect normal users to use git master, don't you think? Yeah, i'm
programmer, compile and run master - no leaks at all. BUT all from 5.4.90 to
5.5.3 has leaks like in pictures above, now backport it to 5.5 brach especially
5.5.3
PS New artwork is quite nice :)

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[via KDE Bugzilla]

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

d...@kaosx.us changed:

   What|Removed |Added

 CC||d...@kaosx.us

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Hugo Pereira Da Costa via KDE Bugzilla]

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

--- Comment #7 from Hugo Pereira Da Costa  ---
(In reply to Anthony from comment #6)
> You cannot expect normal users to use git master, don't you think? Yeah, i'm
> programmer, compile and run master - no leaks at all. BUT all from 5.4.90 to
> 5.5.3 has leaks like in pictures above, now backport it to 5.5 brach
> especially 5.5.3
> PS New artwork is quite nice :)

I repeat: I do not have the leak when running 5.5.3 either
so i would not know what to backport.
I cannot fix a bug that I cannot reproduce.
Only you, who can reproduce the bug, can help me fix it. 
Hence my suggestion to try with more recent code. If this indeed would fix your
problem, next step would be git bisect. 
Then I would be able to identify which change creates the issue (which I cannot
reproduce), and would be able to either backport (indeed), or provide a patch,
or investigate further (with your help).
In the meanwhile, there is not much I can do, sorry.

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #9 from Anthony  ---
https://www.youtube.com/watch?v=IgGnb44NCvA=youtu.be
Video to sure i'm not lying

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

[Breeze] [Bug 357800] Huge leak on X on Kate/Kwrite etc

[Anthony via KDE Bugzilla]

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

--- Comment #8 from Anthony  ---
I don't make fake picture to wrote bug reports, do you agree it? Tested on Arch
and KaOS same result as above.

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