Bug 150130 - kwin crashes on rage128
Summary: kwin crashes on rage128
Status: CLOSED REMIND
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-23 23:26 UTC by Cornholio
Modified: 2007-11-06 16:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cornholio 2007-09-23 23:26:32 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Unspecified Linux
OS:                Linux

kwin crashes very often and this makes the system quite unusable. I cannot replicate the crash since it happens randomly (on application's start, switching between desktops, maximize, minimize etc...).
I have a rage128 card (r128 driver), p3 600.

Note that this bug exists since almost two years.

Here is the trace:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231075616 (LWP 5302)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb78026eb in NETWinInfo::event () from /opt/kde/lib/libkdecore.so.4
#7  0xb67f61e7 in KWinInternal::Client::windowEvent ()
   from /opt/kde/lib/libkdeinit_kwin.so
#8  0xb67f655b in KWinInternal::Workspace::workspaceEvent ()
   from /opt/kde/lib/libkdeinit_kwin.so
#9  0xb67f6dce in KWinInternal::Application::x11EventFilter ()
   from /opt/kde/lib/libkdeinit_kwin.so
#10 0xb7155575 in ?? () from /opt/qt/lib/libqt-mt.so.3
#11 0xbfc37db0 in ?? ()
#12 0xbfc37c88 in ?? ()
#13 0x00000010 in ?? ()
#14 0xb766cdd0 in ?? () from /opt/qt/lib/libqt-mt.so.3
#15 0xb766cdd0 in ?? () from /opt/qt/lib/libqt-mt.so.3
#16 0x00000004 in ?? ()
#17 0xbfc37b98 in ?? ()
#18 0xb7164548 in QApplication::x11ProcessEvent ()
   from /opt/qt/lib/libqt-mt.so.3
Backtrace stopped: frame did not save the PC


Thank you.
Comment 1 Lubos Lunak 2007-09-24 11:19:16 UTC
The backtrace doesn't provide enough information. Please install matching debuginfo packages and try to run kwin in valgrind (valgrind --tool=memcheck --num-callers=40 kwin --replace).
Comment 2 Cornholio 2007-09-24 19:56:38 UTC
where can I find debuginfo files? I have arch linux.
Thank you.
Comment 3 Cornholio 2007-09-25 01:19:19 UTC
I trace the crash with valgrind, and this is the output:


[arch@arch ~]$ valgrind --tool=memcheck --num-callers=40 kwin --replace
==3684== Memcheck, a memory error detector.
==3684== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==3684== Using LibVEX rev 1732, a library for dynamic binary translation.
==3684== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==3684== Using valgrind-3.2.3, a dynamic binary instrumentation framework.
==3684== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==3684== For more details, rerun with: -v
==3684==
--3684-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exit
ing
--3684-- si_code=1;  Faulting address: 0xCA46DBEC;  sp: 0x6220CEB4

valgrind: the 'impossible' happened:
   Killed by fatal signal
==3684==    at 0x3801F9BD: vgPlain_arena_free (in /usr/lib/valgrind/x86-linux/me
mcheck)
==3684==    by 0x3801FB55: vgPlain_free (in /usr/lib/valgrind/x86-linux/memcheck
)
==3684==    by 0x38001967: die_and_free_mem (in /usr/lib/valgrind/x86-linux/memc
heck)
==3684==    by 0x3803728F: vgPlain_scheduler (in /usr/lib/valgrind/x86-linux/mem
check)
==3684==    by 0x38057B91: run_a_thread_NORETURN (in /usr/lib/valgrind/x86-linux
/memcheck)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==3684==    at 0x4020D18: operator delete[](void*) (in /usr/lib/valgrind/x86-lin
ux/vgpreload_memcheck.so)
==3684==    by 0x4BA7C7C: QStringData::deleteSelf() (in /opt/qt/lib/libqt-mt.so.
3.3.8)
==3684==    by 0x4474679: KIconThemeDir::iconPath(QString const&) const (in /opt
/kde/lib/libkdecore.so.4.2.0)
==3684==    by 0x44747B7: KIconTheme::iconPath(QString const&, int, KIcon::Match
Type) const (in /opt/kde/lib/libkdecore.so.4.2.0)
==3684==    by 0x4474CB1: KIconLoader::findMatchingIcon(QString const&, int) con
st (in /opt/kde/lib/libkdecore.so.4.2.0)
==3684==    by 0x449AD15: KIconLoader::loadIcon(QString const&, KIcon::Group, in
t, int, QString*, bool) const (in /opt/kde/lib/libkdecore.so.4.2.0)
==3684==    by 0x44F7118: KWin::icon(unsigned long, int, int, bool, int) (in /op
t/kde/lib/libkdecore.so.4.2.0)
==3684==    by 0x404EF25: KWinInternal::Client::getIcons() (in /opt/kde/lib/libk
deinit_kwin.so)
==3684==    by 0x4085805: KWinInternal::Client::manage(unsigned long, bool) (in
/opt/kde/lib/libkdeinit_kwin.so)
==3684==    by 0x4087675: KWinInternal::Workspace::createClient(unsigned long, b
ool) (in /opt/kde/lib/libkdeinit_kwin.so)
==3684==    by 0x408ACCC: KWinInternal::Workspace::workspaceEvent(_XEvent*) (in
/opt/kde/lib/libkdeinit_kwin.so)
==3684==    by 0x408ADCD: KWinInternal::Application::x11EventFilter(_XEvent*) (i
n /opt/kde/lib/libkdeinit_kwin.so)
==3684==    by 0x481B574: (within /opt/qt/lib/libqt-mt.so.3.3.8)
==3684==    by 0x482A547: QApplication::x11ProcessEvent(_XEvent*) (in /opt/qt/li                                                              b/libqt-mt.so.3.3.8)
==3684==    by 0x483B3AC: QEventLoop::processEvents(unsigned) (in /opt/qt/lib/li                                                              bqt-mt.so.3.3.8)
==3684==    by 0x48A217F: QEventLoop::enterLoop() (in /opt/qt/lib/libqt-mt.so.3.                                                              3.8)
==3684==    by 0x48A2015: QEventLoop::exec() (in /opt/qt/lib/libqt-mt.so.3.3.8)
==3684==    by 0x488B6FE: QApplication::exec() (in /opt/qt/lib/libqt-mt.so.3.3.8                                                              )
==3684==    by 0x4088F42: kdemain (in /opt/kde/lib/libkdeinit_kwin.so)
==3684==    by 0x80485D1: _init (in /opt/kde/bin/kwin)
==3684==    by 0x4FE1F8F: (below main) (in /lib/libc-2.6.1.so)


Note: see also the FAQ.txt in the source distribution.
It contains workarounds to several common problems.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what Linux distro you are using.  Thanks.

[arch@arch ~]$
Comment 4 Lubos Lunak 2007-09-25 14:42:52 UTC
I have no idea, you need to ask on your distribution-specific list/newsgroup/forum/whatever.
Comment 5 Cornholio 2007-09-25 21:42:35 UTC
ok recompiled the glibc, I get this output:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231751456 (LWP 2910)]
[KCrash handler]
#6  0xb774d637 in NETWinInfo::windowType () from /opt/kde/lib/libkdecore.so.4
#7  0xb670e186 in KWinInternal::Client::windowType ()
   from /opt/kde/lib/libkdeinit_kwin.so
#8  0xb670ea91 in KWinInternal::Client::isDesktop ()
   from /opt/kde/lib/libkdeinit_kwin.so
#9  0xb670f2b2 in KWinInternal::Client::isSpecialWindow ()
   from /opt/kde/lib/libkdeinit_kwin.so
#10 0xb67577fd in KWinInternal::findClientInList<KWinInternal::FetchNameInternalPredicate> () from /opt/kde/lib/libkdeinit_kwin.so
#11 0xb6732ace in KWinInternal::Client::setCaption ()
   from /opt/kde/lib/libkdeinit_kwin.so
#12 0xb674c7b0 in KWinInternal::Client::manage ()
   from /opt/kde/lib/libkdeinit_kwin.so
#13 0xb674e676 in KWinInternal::Workspace::createClient ()
   from /opt/kde/lib/libkdeinit_kwin.so
#14 0xb6751ccd in KWinInternal::Workspace::workspaceEvent ()
   from /opt/kde/lib/libkdeinit_kwin.so
#15 0xb6751dce in KWinInternal::Application::x11EventFilter ()
   from /opt/kde/lib/libkdeinit_kwin.so
#16 0xb70b0575 in ?? () from /opt/qt/lib/libqt-mt.so.3
#17 0xbffba0b0 in ?? ()
#18 0xbffb9f88 in ?? ()
#19 0x00100000 in ?? ()
#20 0xb75c7dd0 in ?? () from /opt/qt/lib/libqt-mt.so.3
#21 0xb75c7dd0 in ?? () from /opt/qt/lib/libqt-mt.so.3
#22 0x0000000c in ?? ()
#23 0xbffb9e98 in ?? ()
#24 0xb70bf548 in QApplication::x11ProcessEvent ()
   from /opt/qt/lib/libqt-mt.so.3
Backtrace stopped: frame did not save the PC
Comment 6 Lubos Lunak 2007-09-26 11:07:36 UTC
Sorry, but this is still without any debugging information.
Comment 7 Cornholio 2007-09-27 14:39:29 UTC
hi, this is the correct trace:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232169232 (LWP 2930)]
[KCrash handler]
#6  0xb77fbb5a in NETWinInfo::windowType (this=0x911da80, supported_types=959)
    at netwm.cpp:4394
#7  0xb65eb686 in KWinInternal::Client::windowType (this=0x81df920, 
    direct=false, supported_types=959) at client.cpp:1723
#8  0xb65ee931 in KWinInternal::Client::isDesktop (this=0x81df920)
    at client.cpp:1671
#9  0xb65f0352 in KWinInternal::Client::isSpecialWindow (this=0x81df920)
    at client.cpp:1718
#10 0xb65f0855 in KWinInternal::Client::isMovable (this=0x81df920)
    at geometry.cpp:1608
#11 0xb660b4f9 in KWinInternal::Client::handleMoveResize (this=0x81df920, 
    x=44, y=0, x_root=297, y_root=29) at geometry.cpp:2396
#12 0xb660ca1d in KWinInternal::Client::motionNotifyEvent (this=0x81df920, 
    w=14735385, x=44, y=0, x_root=297, y_root=29) at events.cpp:1356
#13 0xb6617bce in KWinInternal::Client::windowEvent (this=0x81df920, 
    e=0xbf868928) at events.cpp:594
#14 0xb66180e4 in KWinInternal::Workspace::workspaceEvent (this=0x8124bf8, 
    e=0xbf868928) at events.cpp:279
#15 0xb66185fb in KWinInternal::Application::x11EventFilter (this=0xbf868a30, 
    e=0xbf868928) at main.cpp:155
#16 0xb704ce15 in ?? () from /opt/qt/lib/libqt-mt.so.3
#17 0xbf868a30 in ?? ()
#18 0xbf868928 in ?? ()
#19 0x00003fc0 in ?? ()
#20 0xb756cf3c in ?? () from /opt/qt/lib/libqt-mt.so.3
#21 0xb756cf3c in ?? () from /opt/qt/lib/libqt-mt.so.3
#22 0x00000000 in ?? ()
Comment 8 Lubos Lunak 2007-10-01 21:12:08 UTC
I cannot tell much from the backtraces, only that the code is most probably accessing already deleted data. Can you please try again with valgrind, maybe you will manage to get a proper trace without valgrind internal error?
Comment 9 Lubos Lunak 2007-11-06 15:44:12 UTC
Waiting for a response.
Comment 10 Cornholio 2007-11-06 15:59:22 UTC
Hi, sorry for the absence.
I couldn't manage to do what you asked, but I'm realizing that these errors are caused by ram problems (mem86 faults on test 8 and gcc often crashes on segmentation faults).

Thank you for your attention.
KKnull