Bug 251521

Summary: Kwin crash after changing screen resolution
Product: [Plasma] kwin Reporter: Jeff Burns <admiraljkb>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: investigated, triaged
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jeff Burns 2010-09-17 00:22:02 UTC
Application: kwin (4.5.1 (KDE 4.5.1))
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-21-generic x86_64
Distribution: Ubuntu maverick (development branch)

-- Information about the crash:
Occurred on W510 laptop after docking - Using Nvidia Xserver settings tool, changed from LCD panel (1600x900) to external monitors (1900x1200 and 1680x1050) while turning off the LCD panel.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
[Current thread is 1 (Thread 0x7fc8dfe387a0 (LWP 2075))]

Thread 2 (Thread 0x7fc8baf86710 (LWP 2097)):
#0  0x00007fc8df6b62c3 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007fc8dbefc76e in qt_safe_select (nfds=22, fdread=0x3539420, fdwrite=0x35396b8, fdexcept=0x3539950, orig_timeout=0x0) at kernel/qcore_unix.cpp:82
#2  0x00007fc8dbf01beb in QEventDispatcherUNIXPrivate::doSelect (this=0x3539260, flags=<value optimized out>, timeout=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:219
#3  0x00007fc8dbf0281b in QEventDispatcherUNIX::processEvents (this=0x359d770, flags=) at kernel/qeventdispatcher_unix.cpp:919
#4  0x00007fc8dbed1a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fc8dbed1dec in QEventLoop::exec (this=0x7fc8baf85cb0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fc8dbddc2fd in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490
#7  0x00007fc8dbeb15f8 in QInotifyFileSystemWatcherEngine::run (this=0x35384a0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fc8dbddf27e in QThreadPrivate::start (arg=0x35384a0) at thread/qthread_unix.cpp:266
#9  0x00007fc8dd404953 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#10 0x00007fc8dbb54971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#11 0x00007fc8df6bd92d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fc8dfe387a0 (LWP 2075)):
[KCrash Handler]
#6  0x00007fc8df60aba5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fc8df60e6b0 in abort () at abort.c:92
#8  0x00007fc8df64443b in __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007fc8df64e4b6 in malloc_printerr (action=3, str=0x7fc8df71eca2 "corrupted double-linked list", ptr=<value optimized out>) at malloc.c:6283
#10 0x00007fc8df64e961 in malloc_consolidate (av=<value optimized out>) at malloc.c:5169
#11 0x00007fc8df651350 in _int_free (av=0x7fc8df955e40, p=0x430d640) at malloc.c:5034
#12 0x00007fc8df654c83 in __libc_free (mem=<value optimized out>) at malloc.c:3738
#13 0x00007fc8d4cb4a44 in ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.260.19.04
#14 0x00007fc8d4d11288 in ?? () from /usr/lib/nvidia-current/libnvidia-glcore.so.260.19.04
#15 0x00007fc8ddffbbdf in KWin::GLTexture::discard (this=0x44f5b80) at ../../../kwin/lib/kwinglutils.cpp:483
#16 0x00007fc8dfa1f712 in KWin::SceneOpenGL::Window::discardTexture (this=0x44f5ac0) at ../../kwin/scene_opengl.cpp:1333
#17 0x00007fc8dfa1f823 in KWin::SceneOpenGL::Window::~Window (this=0x81b, __in_chrg=<value optimized out>) at ../../kwin/scene_opengl.cpp:1304
#18 0x00007fc8dfa20d8c in KWin::SceneOpenGL::windowClosed (this=0x2881140, c=0x44ed360, deleted=0x0) at ../../kwin/scene_opengl.cpp:933
#19 0x00007fc8dfa0d639 in KWin::Workspace::finishCompositing (this=0x2723050) at ../../kwin/composite.cpp:257
#20 0x00007fc8dfa0e186 in KWin::Workspace::resetCompositing (this=0x2723050) at ../../kwin/composite.cpp:357
#21 0x00007fc8df99034d in KWin::Workspace::qt_metacall (this=0x2723050, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffb6241330) at ./workspace.moc:531
#22 0x00007fc8dbeeab27 in QMetaObject::activate (sender=0x27235c8, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xffffffffffffffff) at kernel/qobject.cpp:3280
#23 0x00007fc8dbee48f9 in QObject::event (this=0x27235c8, e=0x81b) at kernel/qobject.cpp:1183
#24 0x00007fc8db01e04c in QApplicationPrivate::notify_helper (this=0x2624170, receiver=0x27235c8, e=0x7fffb6241a80) at kernel/qapplication.cpp:4396
#25 0x00007fc8db023b5d in QApplication::notify (this=0x7fffb6241e70, receiver=0x27235c8, e=0x7fffb6241a80) at kernel/qapplication.cpp:4277
#26 0x00007fc8df1b9156 in KApplication::notify (this=0x7fffb6241e70, receiver=0x27235c8, event=0x7fffb6241a80) at ../../kdeui/kernel/kapplication.cpp:310
#27 0x00007fc8dbed2cdc in QCoreApplication::notifyInternal (this=0x7fffb6241e70, receiver=0x27235c8, event=0x7fffb6241a80) at kernel/qcoreapplication.cpp:732
#28 0x00007fc8dbf026f2 in sendEvent (this=0x2624b80) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#29 QTimerInfoList::activateTimers (this=0x2624b80) at kernel/qeventdispatcher_unix.cpp:602
#30 0x00007fc8dbf0282c in QEventDispatcherUNIX::processEvents (this=0x25ffee0, flags=) at kernel/qeventdispatcher_unix.cpp:923
#31 0x00007fc8db0d1a3f in QEventDispatcherX11::processEvents (this=<value optimized out>, flags=) at kernel/qeventdispatcher_x11.cpp:152
#32 0x00007fc8dbed1a02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#33 0x00007fc8dbed1dec in QEventLoop::exec (this=0x7fffb6241db0, flags=) at kernel/qeventloop.cpp:201
#34 0x00007fc8dbed5ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#35 0x00007fc8df9acf7d in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kwin/main.cpp:531
#36 0x00007fc8df5f5d8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffb6242478) at libc-start.c:226
#37 0x0000000000400669 in _start ()

Possible duplicates by query: bug 208881.

Reported using DrKonqi
Comment 1 Thomas Lübking 2010-09-17 15:02:19 UTC
crashes in nvidias blob, glDeleteTextures(), causing or caused by a mem corruption

- 260 is still the beta driver?
- is this reproducible? (if you do exact the same, the exact smae happens again?)

-> to workaround the issue, suspend compositing (SHIFT+ALT+F12) before changing screen/resolution (plain resolution changes via xrandr should be ok, afaics)
toggle again to resume compositing
Comment 2 Jeff Burns 2010-09-17 17:59:07 UTC
260.19.04 is a beta driver.

Sorry, I can't reproduce at will...  I switch screens and resolution 2-3 (or more) times a day, and have been running that driver for a week or two.

Thanks for the workaround.  At this point I won't use it so as to catch more data.
Comment 3 Andrew Crouthamel 2018-09-20 22:01:55 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 05:26:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!