Bug 276589 - Kontact crashes on closing
Summary: Kontact crashes on closing
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: calendar (show other bugs)
Version: 4.7 pre
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-27 05:29 UTC by Torbjörn K.
Modified: 2017-01-07 22:08 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 Torbjörn K. 2011-06-27 05:29:48 UTC
Application: kontact (4.7 pre)
KDE Platform Version: 4.6.80 (4.7 Beta1) "release 6"
Qt Version: 4.7.3
Operating System: Linux 2.6.37.6-0.5-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

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

Crash when closing Kontact.

It might be in relation with KOrganizer, as it happend, while the KOrganizer view was open.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7faf71057760 (LWP 13562))]

Thread 2 (Thread 0x7faf5ab0d700 (LWP 13563)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007faf6da801d4 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#2  0x00007faf693a8a3f in start_thread (arg=0x7faf5ab0d700) at pthread_create.c:297
#3  0x00007faf6e62267d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7faf71057760 (LWP 13562)):
[KCrash Handler]
#6  0x00007faf6e581ab5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007faf6e582fb6 in abort () at abort.c:92
#8  0x00007faf6e5bcdd3 in __libc_message (do_abort=2, fmt=0x7faf6e67d9b0 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:186
#9  0x00007faf6e5c23b6 in malloc_printerr (action=3, str=0x7faf6e67ab7e "free(): invalid pointer", ptr=<value optimized out>) at malloc.c:6261
#10 0x00007faf4ccf38c5 in ~QByteArray (this=0x1cd9fe0) at /usr/include/QtCore/qbytearray.h:383
#11 BaseConfig::usrReadConfig (this=0x1cd9fe0) at /usr/src/debug/kdepim-4.6.80/calendarviews/eventviews/prefs.cpp:202
#12 0x00007faf6fdbbb33 in KCoreConfigSkeleton::writeConfig (this=0x1cd9fe0) at /usr/src/debug/kdelibs-4.6.80/kdecore/config/kcoreconfigskeleton.cpp:1086
#13 0x00007faf4ccf09dc in EventViews::Prefs::writeConfig (this=0x1cc9440) at /usr/src/debug/kdepim-4.6.80/calendarviews/eventviews/prefs.cpp:547
#14 0x00007faf4d38332e in KOPrefs::~KOPrefs (this=0x21b5d20, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.6.80/korganizer/koprefs.cpp:85
#15 0x00007faf4d383589 in KOPrefs::~KOPrefs (this=0x21b5d20, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.6.80/korganizer/koprefs.cpp:86
#16 0x00007faf4d3831bd in ~KOPrefsPrivate () at /usr/src/debug/kdepim-4.6.80/korganizer/koprefs.cpp:56
#17 destroy () at /usr/src/debug/kdepim-4.6.80/korganizer/koprefs.cpp:60
#18 0x00007faf6e5845a1 in __run_exit_handlers (status=0, listp=0x7faf6e8b64a8, run_list_atexit=true) at exit.c:78
#19 0x00007faf6e5845f5 in exit (status=13562) at exit.c:100
#20 0x00007faf6e56dc04 in __libc_start_main (main=0x403510 <main(int, char**)>, argc=1, ubp_av=0x7fff8ded02c8, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff8ded02b8) at libc-start.c:258
#21 0x0000000000402e79 in _start () at ../sysdeps/x86_64/elf/start.S:113

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 19:20:09 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:08:17 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.