nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   180.60: glibc double free in libGL at logout from KDE 4.2.3 (http://www.nvnews.net/vbulletin/showthread.php?t=133969)

dae 06-03-09 06:04 AM

180.60: glibc double free in libGL at logout from KDE 4.2.3
 
2 Attachment(s)
When logging out from KDE (4.2.3), I get:

QPainter::begin: Cannot paint on a null pixmap
QPainter::setCompositionMode: Painter not active
kwin(3577) KWin::x11ErrorHandler: kwin: X Error ( "error: BadDamage [DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x10001f5" )
kwin(3577) KWin::x11ErrorHandler: kwin: X Error ( "error: BadDamage [DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x10001f9" )
kwin(3577) KWin::x11ErrorHandler: kwin: X Error ( "error: BadDamage [DAMAGE+0], request: XDamageDestroy[DAMAGE+2], resource: 0x10001f8" )
*** glibc detected *** kwin: double free or corruption (!prev): 0x0000000001c84840 ***
======= Backtrace: =========
/lib64/libc.so.6[0x7fad78e17175]
/lib64/libc.so.6(cfree+0x10c)[0x7fad78e1be4c]
/usr/lib64/libGL.so.1[0x7fad7944bec8]

This has been happening for some time now, and I'm not sure in exactly which driver version it started. It's almost 100% reproducable, although sometimes kwin simply crashes, without the double free. I see it happening on both my nvidia systems.

Someone else posted something that looks very similar to the KDE bug tracker, and the KDE devs pointed at nvidia: https://bugs.kde.org/show_bug.cgi?id=187769

Just like the bug reporting howto said, I generated the bug report after the problem occured, which is after X is killed, meaning some information in the bug report is missing. Let me know if you want me to regenerate it with X running.

I'll also attach the complete output from X/KDE when it crashes.

Linux: 2.6.29.4
QT: 4.5.1
KDE: 4.2.3

dae 06-03-09 09:04 AM

Re: 180.60: glibc double free in libGL at logout from KDE 4.2.3
 
Note that the title is slightly misleading - the driver version in the logs is 185.18.10. On my other system, where I see exactly the same crash, I'm running 180.60.


All times are GMT -5. The time now is 12:16 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.