Version: (using KDE 4.1.0) OS: Linux Installed from: Fedora RPMs I'm testing nVidia's latest beta drivers. (v177.67) I've partially enabled desktop effects. After 2-3 hours of use, kwin started eating CPU (>40%) and the following error appear in .xsession_errors $ cat .xsession-errors | grep BadPixmap kwin: X Error (error: BadPixmap [4], request: X_FreePixmap[54], resource: 0x160577c) kwin: X Error (error: BadPixmap [4], request: X_FreePixmap[54], resource: 0x160577d) kwin: X Error (error: BadPixmap [4], request: X_FreePixmap[54], resource: 0x160577e) ... $ cat .xsession-errors | grep BadPixmap | wc -l 751 Fedora 9, x86_64, KDE 4.1 (updates/testing) - Gilboa
Have you experienced this problem with the stable driver as well? I just tested on my machine and I have 10 such lines after nearly 10 h uptime (although compositing was disable for some time).
The stable driver has severe Xrender problems. Using it w/ KDE 4.1 is pure torture. (At least on my 9800GTX) Can you enable kwin composition for a couple of hours and see if you can reproduce this problem? - Gilboa
I've never noticed this. Please reopen if you can reproduce using stable drivers.
I've switched to stable drivers (v173.14.12), and I'm seeing more-or-less the same problem. (Different error, both on close) $ cat .xsession-errors | grep "kwin: X Error" kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1801cff) kwin: X Error (error: BadMatch [8], request: X_SetInputFocus[42], resource: 0x5200001) kwin: X Error (error: BadMatch [8], request: X_SetInputFocus[42], resource: 0x5200001) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x180298c) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x180298f) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1802992) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1802998) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1803045) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18036e6) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18036e9) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18036ec) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18036ef) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18036f2) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x18036f5) Still looks like an nVidia bug? - Gilboa
How can you see a problem with pixmaps leaking only on close?
The problem (at least AFAIKS) is not memory leaks - but the reason for the memory leaks. If I understand correctly, the X resource pointer are somehow screwed, causing the close to fail. As the actual resource don't get released, memory leak occurs. As I'm not that familiar with Xlib and friends, I'm just guess. Can I somehow get a listing of all valid Xlib objects being used by kwin? - Gilboa
The warnings should be harmless, and definitely not cause huge memory leaks. Since you haven't confirmed any leaks with the stable driver, I still see no bug.
OK. I'll post a bug report in nvnews.com. Thanks, Gilboa
I'm having the same behavior with an Intel card in Kubuntu Hardy (KDE 4.1 too). After some hours, KWin starts to feel laggy and sometimes it starts eating CPU to the point that it makes the system unusable and I have to reset the machine.
I am experiencing the same problems... These are the final lines of my .xsession-errors file: kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1426644) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1426e86) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x14278bd) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1427ab6) QObject: Do not delete object, 'unnamed', during its event handler! kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x142b133) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x142baed) e kwin: X Error (error: BadMatch [8], request: X_SetInputFocus[42], resource: 0x30deb80) X Error: BadWindow (invalid Window parameter) 3 Major opcode: 2 (X_ChangeWindowAttributes) Resource id: 0x30dee5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x3da70f5 kwin: X Error (error: BadPixmap [4], request: X_FreePixmap[54], resource: 0x142e3f5) kwin: X Error (error: BadMatch [8], request: X_SetInputFocus[42], resource: 0x30e031c) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x142f6fc) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x142f8c5) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1430d6e) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1430d6f) kwin: X Error (error: BadPixmap [4], request: X_FreePixmap[54], resource: 0x1430ecd) This is happens using an ATI card with the latest proprietary driver on KDE 4.1.2 (Gentoo).
I am experiencing the same problems... With ubuntu 8.10 x86_64, GeForce 6600 GT, NVIDIA Driver Version:177.80 When activating kwin effects, cpu > 40% and Xorg memory grows up And then X goes black or freeze When compositing is off, cpu is lower but memory stays up. with this lines in .xsessions-errors: kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1407aa7) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1407b46) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1407b9a) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1407eaf) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1407ebb) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1408030) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1408033) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1408827) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x140896c) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1408c1d) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1408da3) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x14093b3) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1409594)
Please file a separate bugreport for your separate issue. "When activating kwin effects, cpu > 40% and Xorg memory grows up" is not "kwin's effects are leaking pixmaps" just because the guessed cpu usage happens to be a similar number.
Lubos Lunak, While parts of his bug report seem unrelated (Xorg goes blank, etc) - I should mention that once the leak party begins, CPU usage goes sky-high; Seems to be that he's hitting the same issue (at a somewhat elevated state...) - Gilboa P.S. If indeed ATI users are seeing the same bug, is it possible that it isn't an nVidia bug after-all?
Ok seems to be a nvidia bug. Tested with GeForce5500 -> no problem.
I'm seeing the same symptoms as many others with the current intel git master drivers+xorg, DRI2 etc. KWin from svn.
This is not nvidia specific i get it with radeon driver too kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x140cb7f) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x140cc52) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x140db3d) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x140dbd5) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x140f1fa) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1410277) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x141027a) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1410280) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x14107e5) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x14108e8) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x14108eb) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x14108f2) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1410970) kwin: X Error (error: <unknown>[DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x1410a46)