Bug 263134 - KDevelop crashes at exit
Summary: KDevelop crashes at exit
Status: RESOLVED DUPLICATE of bug 261111
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 4.2.0
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-14 13:00 UTC by serbay
Modified: 2011-01-14 14:00 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 serbay 2011-01-14 13:00:30 UTC
Application: kdevelop (4.1.2)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-24-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:

KDevelop is again crashing at exit. Some guy told me it is going to be fixed in 4.1.2 but it doesn't seem to be fixed.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Aborted
[Current thread is 1 (Thread 0x7f51c51d1760 (LWP 17508))]

Thread 3 (Thread 0x7f51b4844700 (LWP 17509)):
#0  0x00007f51c2654203 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f51bc693009 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007f51bc6937b5 in g_main_loop_run () from /lib/libglib-2.0.so.0
#3  0x00007f51b4f7b0f4 in ?? () from /usr/lib/libgio-2.0.so.0
#4  0x00007f51bc6b87e4 in ?? () from /lib/libglib-2.0.so.0
#5  0x00007f51c2364971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6  0x00007f51c266092d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f51a65f8700 (LWP 17510)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:212
#1  0x00007f51c3960da2 in wait (this=<value optimized out>, mutex=0x1f47fa0, time=200000) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x1f47fa0, time=200000) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f51bfab2a2e in KDevelop::DUChainPrivate::CleanupThread::run (this=0x1f47f80) at ../../language/duchain/duchain.cpp:287
#4  0x00007f51c396027e in QThreadPrivate::start (arg=0x1f47f80) at thread/qthread_unix.cpp:266
#5  0x00007f51c2364971 in start_thread (arg=<value optimized out>) at pthread_create.c:304
#6  0x00007f51c266092d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f51c51d1760 (LWP 17508)):
[KCrash Handler]
#6  0x00007f51c25adba5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007f51c25b16b0 in abort () at abort.c:92
#8  0x00007f51c25e743b in __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9  0x00007f51c25f14b6 in malloc_printerr (action=3, str=0x7f51c26c5030 "double free or corruption (fasttop)", ptr=<value optimized out>) at malloc.c:6283
#10 0x00007f51c25f7c83 in __libc_free (mem=<value optimized out>) at malloc.c:3738
#11 0x00007f51c25b34f2 in __run_exit_handlers (status=0) at exit.c:78
#12 exit (status=0) at exit.c:100
#13 0x00007f51c2598d95 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=0x7fffe69a6e58) at libc-start.c:258
#14 0x0000000000403789 in _start ()

Possible duplicates by query: bug 262108, bug 262106, bug 261111, bug 257944, bug 255982.

Reported using DrKonqi
Comment 1 serbay 2011-01-14 13:03:12 UTC
By the way, I have just realized that, it happens when i disabled Git Support plugin to avoid the error message at start, which was something like "Process exited with status 0". I thought it might be helpful.
Comment 2 Milian Wolff 2011-01-14 14:00:32 UTC
seems unrelated to git, I'll add some infos to bug 261111, please read that and try to provide more insight

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