Bug 255861 - Kontact crash while opening IMAP mailbox
Summary: Kontact crash while opening IMAP mailbox
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources FreeBSD
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-02 10:11 UTC by Joe Kraft
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 Joe Kraft 2010-11-02 10:11:01 UTC
Application: kontact (4.4.7)
KDE Platform Version: 4.5.2 (KDE 4.5.2) (Compiled from sources)
Qt Version: 4.6.3
Operating System: FreeBSD 8.1-STABLE i386
Distribution (Platform): FreeBSD Ports

-- Information about the crash:
- What I was doing when the application crashed:
	I was switching from one IMAP mailbox to another.  When the screen showing please wait came up, I clicked the inbox folder again.  As soon as the mailbox was displayed Kontact crashed.
- Unusual behavior I noticed:
	Kontact was using a 430M of memory, which had grown substantially as I left it open overnight.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Kontact (kontact), signal: Abort trap: 6
[Current thread is 1 (Thread 326cf640 (LWP 100367))]

Thread 2 (Thread 2cd01140 (LWP 100283)):
[KCrash Handler]
#7  0x2b52c1fb in thr_kill () from /lib/libc.so.7
#8  0x2b4db886 in pthread_kill () from /lib/libthr.so.3
#9  0x2b4d93b3 in raise () from /lib/libthr.so.3
#10 0x2b5cf16a in abort () from /lib/libc.so.7
#11 0x2b41ece0 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6
#12 0x2b4234ea in std::set_unexpected () from /usr/lib/libstdc++.so.6
#13 0x2b423532 in std::terminate () from /usr/lib/libstdc++.so.6
#14 0x2b4233b8 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#15 0x2af69e05 in QCoreApplication::notifyInternal () from /usr/local/lib/qt4/libQtCore.so.4
#16 0x2af99b04 in QTimerInfoList::activateTimers () from /usr/local/lib/qt4/libQtCore.so.4
#17 0x2af97464 in timerSourceDispatch () from /usr/local/lib/qt4/libQtCore.so.4
#18 0x2c4bb817 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0
#19 0x2c4bf05e in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0
#20 0x2c4bf685 in g_main_context_iteration () from /usr/local/lib/libglib-2.0.so.0
#21 0x2af978eb in QEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtCore.so.4
#22 0x2a15d585 in QGuiEventDispatcherGlib::processEvents () from /usr/local/lib/qt4/libQtGui.so.4
#23 0x2af68df3 in QEventLoop::processEvents () from /usr/local/lib/qt4/libQtCore.so.4
#24 0x2af6916a in QEventLoop::exec () from /usr/local/lib/qt4/libQtCore.so.4
#25 0x2af6b5e6 in QCoreApplication::exec () from /usr/local/lib/qt4/libQtCore.so.4
#26 0x2a0a2887 in QApplication::exec () from /usr/local/lib/qt4/libQtGui.so.4
#27 0x0804bb3f in ?? ()
#28 0x0804a6a7 in ?? ()
#29 0x00000001 in ?? ()
#30 0xbfbfe7e4 in ?? ()
#31 0xbfbfe7ec in ?? ()
#32 0xbfbfe7d0 in ?? ()
#33 0xbfbfe7e0 in ?? ()
#34 0x00000000 in ?? ()
#35 0xbfbfe7dc in ?? ()
#36 0x0804a615 in ?? ()

Thread 1 (Thread 326cf640 (LWP 100367)):
#0  0x2b5b75ab in kevent () from /lib/libc.so.7
#1  0x2af4b738 in QKqueueFileSystemWatcherEngine::run () from /usr/local/lib/qt4/libQtCore.so.4
#2  0x2ae64857 in QThreadPrivate::start () from /usr/local/lib/qt4/libQtCore.so.4
#3  0x2b4d575f in pthread_getprio () from /lib/libthr.so.3
#4  0x00000000 in ?? ()

Possible duplicates by query: bug 171364.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 19:23:16 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:31 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.