Bug 269214 - KWin crashes at seemingly random points
Summary: KWin crashes at seemingly random points
Status: RESOLVED DUPLICATE of bug 241163
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-23 11:27 UTC by braggrj
Modified: 2011-03-23 14:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description braggrj 2011-03-23 11:27:53 UTC 
Application: kwin (4.6.00 (4.6.0) "release 6")
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-1.2-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
Using Firefox 4 in OpenSUSE 11.4 64bit.

Not a complex site.  Internal site using JQuery and other bits of JavaScript.

Running kvpn to connect to work Network and one Konsole window open in background.

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

Thread 2 (Thread 0x7f21beebd700 (LWP 4319)):
#0  0x00007f21d4bc538c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f21d7a49044 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f21d7d62180) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f21d7a49079 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f21d7d70254) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f21d4bc0a3f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f21d8bdb67d in clone () from /lib64/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f21d937d7a0 (LWP 4282)):
[KCrash Handler]
#6  0x00007f21d8b3aab5 in raise () from /lib64/libc.so.6
#7  0x00007f21d8b3bfb6 in abort () from /lib64/libc.so.6
#8  0x00007f21d3cd3a9d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#9  0x00007f21d3cd1cb6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x00007f21d3cd1ce3 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x00007f21d3cd1e36 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#12 0x00007f21d4f38333 in QEventLoop::exec (this=0x7fff763309c0, flags=...) at kernel/qeventloop.cpp:214
#13 0x00007f21d4f3c6ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#14 0x00007f21d8ed0c8a in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#15 0x00007f21d8b26bfd in __libc_start_main () from /lib64/libc.so.6
#16 0x0000000000400699 in _start ()

Possible duplicates by query: bug 269168, bug 269148, bug 269112, bug 269092, bug 268998.

Reported using DrKonqi
Comment 1 Thomas Lübking 2011-03-23 14:46:12 UTC 
see the dupe.
it's not sure if it actually is (you'll have to get a trace using gdb as described over there), but there's no way to ultimately say from this backtrace (and you won't get a better one)

In general, setting the scale method to "smooth" rather than "accurate" would workaround this.

*** This bug has been marked as a duplicate of bug 241163 ***