[Bug Report] KDE4 Plasma looses theming and fonts with 180.44/180.51/185.19

[save]

Hi,

since several month I've the problem that running KDE 4.2.2 some time ( 2-3 h ) the plasma desktop "looses" its theming and fails to display fonts. (please see attached screenshots of how this looks).
At the time as this happens I've the following messages in my $HOME/.xsessions log file:

...
In file image/qpixmap_x11.cpp, line 1424: Out of memory
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
...

If I kill & restart plasma everything is fine for the next 2 - 3 hours. I've talked to some plasma guys if this behaviour could be plasma's fault but they told me that this is not the case instead they pointed out it could be a memory leak caused by the nvidia drivers.

I've attached the nvidia_bug_report log and an abstract of my .xsession log. Please let me know if there is information missing which helps you to debug this error.

My Setup:

Intel Quad Core CPU
GeForce 8500 GT (rev a1)
180.51 nvidia driver

[jui]

I have the same problem since I use KDE 4 (4.1, 4.2, 4.2.2). NV Driver version is: 180.44-0.1, I have 64 bit architecture and NV GForce 7800 GT.

QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted


Any idea ?

[AaronP]

It's pretty unlikely that this is caused by a memory leak in the NVIDIA driver. More likely, plasma is leaking pixmaps or client-side X resources. A good first step would be to determine which process has the leak: when the errors start occurring, does top report a lot of memory allocated to the plasma process? Likewise, please run xrestop and see how much memory it attributes to the plasma process.

[jui]

I didn't noticed anything special using xrestop after and before QPainter crash bottom bar:

Before:
xrestop - Display: localhost:0
Monitoring 53 clients. XErrors: 0
Pixmaps: 82719K total, Other: 171K total, All: 82891K total

res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier
5200000 22 11 0 373 449 14508K 11K 14520K 32466 Qt-subapplication
1600000 129 2 0 356 836 12435K 22K 12458K 4520 kwin
4600000 0 22 0 35 32 7458K 1K 7459K ? <unknown>
6400000 0 22 0 25 21 7225K 1K 7226K ? <unknown>
5600000 8 5 0 210 266 4095K 6K 4101K 30957 Krusader
2e00000 8 2 0 135 200 3011K 4K 3016K 31475 CZ-Tunes - Silent Service II :: Amarok 2
1200000 6 2 0 51 79 200K 2K 202K 4744 kupdateapplet
5400000 3 1 0 48 61 170K 1K 171K 29984 kdesu
0800000 7 1 0 24 47 154K 1K 155K 4584 kmix
1800000 5 1 0 129 173 149K 4K 153K 4561 Qt-subapplication

After:
xrestop - Display: localhost:0
Monitoring 50 clients. XErrors: 0
Pixmaps: 107149K total, Other: 226K total, All: 107376K total

res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier
5200000 24 14 0 2855 2958 28273K 70K 28343K 29957 Qt-subapplication
1600000 121 2 0 357 823 26840K 22K 26863K 4520 kwin
4600000 0 22 0 35 32 7458K 1K 7459K ? <unknown>
6400000 0 22 0 25 21 7225K 1K 7226K ? <unknown>
5600000 8 5 0 210 266 4095K 6K 4101K 30957 Krusader
2e00000 8 2 0 135 197 3011K 4K 3016K 31475 CZ-Tunes - Silent Service II :: Amarok 2
1200000 6 2 0 51 78 200K 2K 202K 4744 kupdateapplet
5400000 3 1 0 48 61 170K 1K 171K 29984 kdesu
0800000 7 1 0 24 46 154K 1K 155K 4584 kmix
1800000 5 1 0 129 171 149K 4K 153K 4561 Qt-subapplication

It's happen randomly. 3-5 hours all is ok, and suddenly bottom bar (task manager) disappear or stop working properly and I get loop message:

QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active

I have tried reinstall KDE, install different QT versions - no results.

[Smertios]

Hello,

I can confirm this bug on my system here as well. It's the latest Kubuntu 9.04 (KDE 4.2.2) on an AMD64 running a GeForce 9500 GT with driver 180.44 from Ubuntu repository.

I get the same bunch of messages:

QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setCompositionMode: Painter not active
QPainter::end: Painter not active, aborted

xrestop does not show any peculiarities:

xrestop - Display: :1
          Monitoring 53 clients. XErrors: 8
          Pixmaps:  153433K total, Other:     448K total, All:  153881K total

res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID Identifier
1c00000    38   20    0 4729 4855    40245K    115K  40360K 24884 Qt-subapplication

Please find my nvidia-bug-report.log attached to this post.
Thank you for your consideration of this matter.

[save]

I've posted the link to this forum post to the plasma developer list with the hope that someone of the guys comment on this bug.

[wolf08]

I seem to remember some talk a few days ago about a Qt bug where X pixmaps were leaked when things were inserted into a cache with the same key.

[jui]

Tomorrow I'll try new KDE 4.3 on openSUSE 11.1. I hope this bug will be fixed...

[Nico.Laus]

can't be an NVidia driver bug, because I got this at work (ATI FireGL, open source radeon driver) and on my laptop (intel graphics driver) as well -> must be a plasma bug (very annoying though)
btw: to follow the mailing list without being subscribed to it, here's the link to the mail "save" was referring to: http://mail.kde.org/pipermail/plasma...ay/005526.html

I already had a quick look into reporting that to the kde bug system but found lots of plasma-related bugs and wasn't quite sure how to name this one (it might have even been in there already - some sounded quite alike),
@save: since you already have the bugtraces, could you maybe have another look into that and report that? - you might post a link here for us to vote on it

[save]

The plasma bug is discussed here:

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

Aaron Seigo discussed the pixmap leaking leaking bug in his blog:

http://aseigo.blogspot.com/2009/04/p...ory-usage.html

[kernelOfTruth]

*subscribes*

I'll let kde4 run for some hours and then see whether that triggers it too for me (running 185.18.08 on ~amd64, Gentoo)

kde 4.3svn latest from a few days ago

[jui]

@save thx for the links. I'll disabled seconds in my digital clock widget and now plasma is stable