Bug 200922 - Lancelot crashed randomly while using KDevelop
Summary: Lancelot crashed randomly while using KDevelop
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-lancelot (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-20 21:23 UTC by Stefan Stammberger
Modified: 2009-09-14 10:40 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Stammberger 2009-07-20 21:23:35 UTC
Application that crashed: lancelot
Version of the application: 1.7
KDE Version: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
Qt Version: 4.5.0
Operating System: Linux 2.6.28-13-generic x86_64
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I was just using KDevelop and the KCrashHandler poped up. I was not even near Lancelot with my mouse. I had not used it for quite a while.

 -- Backtrace:
Application: Lancelot (lancelot), signal: Aborted
[KCrash Handler]
#5  0x00007fe530e94fb5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007fe530e96bc3 in *__GI_abort () at abort.c:88
#7  0x00007fe530ed4228 in __libc_message (do_abort=2, fmt=0x7fe530f9e488 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:170
#8  0x00007fe530ed9cb8 in malloc_printerr (action=2, str=0x7fe530f9e500 "free(): invalid next size (normal)", ptr=<value optimized out>) at malloc.c:5994
#9  0x00007fe530edc276 in *__GI___libc_free (mem=0x7fe530f948a0) at malloc.c:3625
#10 0x00007fe532c918d9 in ~QDBusMessagePrivate (this=0x2187730) at ./qdbus_symbols_p.h:289
#11 0x00007fe532c91b52 in ~QDBusMessage (this=<value optimized out>) at qdbusmessage.cpp:491
#12 0x00007fe532c8fccd in ~QDBusCallDeliveryEvent (this=0x24b9450) at qdbusintegrator_p.h:92
#13 0x00007fe53296b3d9 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1973080) at kernel/qcoreapplication.cpp:1255
#14 0x00007fe5329941e3 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#15 0x00007fe52b47720a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x00007fe52b47a8e0 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x00007fe52b47aa7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0x00007fe532993e6f in QEventDispatcherGlib::processEvents (this=0x1972e30, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#19 0x00007fe531becbef in QGuiEventDispatcherGlib::processEvents (this=0xe10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#20 0x00007fe532969002 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1028995008}) at kernel/qeventloop.cpp:149
#21 0x00007fe5329693cd in QEventLoop::exec (this=0x7fff3d553800, flags={i = 1028995088}) at kernel/qeventloop.cpp:200
#22 0x00007fe53296b694 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#23 0x00000000004348c7 in _start ()

Reported using DrKonqi
Comment 1 Ivan Čukić 2009-09-14 10:40:18 UTC
Since I've received no confirmation of this bug, and I'm not able to reproduce, I'm closing it.

BTW, it looks like a problem/bug of Qt+Dbus