Subject: Re:  New: kmail crashed after mouse click in folder window

Hi Eva,

This looks like a 'typical' KMail IMAP crash.

Unfortunately KMails IMAP implementation is somewhat unstable 
especially on slower IMAP servers.

Now I do hope to revise KMail's IMAP code but this is a major 
undertaking.

What would encourage me to do that work is if you could file a general 
IMAP is unstable bug report collect as much specific information as 
possible (like the info you have provided below it is valuable), vote 
this bug up on bugs.kde.org and encourage others to do so also. (The 
more votes the higher precedence I give the task).

This would tie in with my future voteawish.org hopes.
See "I'm also about to put...."
http://lists.kde.org/?l=kde-pim&m=104063510209104&w=2

Thanks for your time,
Don.

On Monday 30 December 2002 00:15, eva@kde.org wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=52386
>            Summary: kmail crashed after mouse click in folder
> window Product: kmail
>            Version: unspecified
>           Platform: Compiled Sources
>         OS/Version: Linux
>             Status: NEW
>           Severity: crash
>           Priority: NOR
>          Component: general
>         AssignedTo: kmail@kde.org
>         ReportedBy: eva@kde.org
>
>
> Version:            (using KDE Devel)
> Installed from:    Compiled sources
> Compiler:          gcc-3.2 suse 8.1
> OS:          Linux
>
> It's not easily reproducable, since usually it works... hopefully
> the backtrace helps.
>
> [New Thread 1024 (LWP 1333)]
> 0x417ec8c9 in wait4 () from /lib/libc.so.6
> #0  0x417ec8c9 in wait4 () from /lib/libc.so.6
> #1  0x41867c90 in __DTOR_END__ () from /lib/libc.so.6
> #2  0x41647a93 in waitpid () from /lib/libpthread.so.0
> #3  0x40af98bd in KCrash::defaultCrashHandler(int) ()
>    from /opt/kde3_1/lib/libkdecore.so.4
> #4  0x4164512b in pthread_sighandler () from /lib/libpthread.so.0
> #5  <signal handler called>
> #6  0x40e13bfe in QShared::ref() (this=0xbfffed90) at
> ../include/qshared.h:49 #7  0x41209960 in QString (this=0xbfffed90,
> s=@0x848d2a0)
>     at tools/qstring.cpp:13189
> #8  0x4060de4b in KIO::Scheduler::_assignJobToSlave(KIO::Slave*,
> KIO::SimpleJob*) () from /opt/kde3_1/lib/libkio.so.4 #9  0x081a23d2
> in KMAcctImap::slotIdleTimeout() ()
> #10 0x0819fbd9 in KMAcctImap::qt_invoke(int, QUObject*) ()
> #11 0x40ef1848 in QObject::activate_signal(QConnectionList*,
> QUObject*) ( this=0x8690520, clist=0x84739d0, o=0xbfffef20) at
> kernel/qobject.cpp:2212 #12 0x40ef16cf in
> QObject::activate_signal(int) (this=0x8690520, signal=2) at
> kernel/qobject.cpp:2186
> #13 0x4127a5a8 in QTimer::timeout() (this=0x8690520)
>     at .moc/debug-shared-mt/moc_qtimer.cpp:82
> #14 0x40f1cc61 in QTimer::event(QEvent*) (this=0x8690520,
> e=0xbffff1b0) at kernel/qtimer.cpp:219
> #15 0x40e7a7a4 in QApplication::internalNotify(QObject*, QEvent*) (
>     this=0xbffff570, receiver=0x8690520, e=0xbffff1b0)
>     at kernel/qapplication.cpp:2350
> #16 0x40e79c65 in QApplication::notify(QObject*, QEvent*)
> (this=0xbffff570, receiver=0x8690520, e=0xbffff1b0) at
> kernel/qapplication.cpp:2112 #17 0x40a7db49 in
> KApplication::notify(QObject*, QEvent*) () from
> /opt/kde3_1/lib/libkdecore.so.4
> #18 0x40e12ecf in QApplication::sendEvent(QObject*, QEvent*) (
>     receiver=0x8690520, event=0xbffff1b0) at
> kernel/qapplication.h:478 #19 0x40e4c9ff in
> QEventLoop::activateTimers() (this=0x82cd778) at
> kernel/qeventloop_unix.cpp:524
> #20 0x40e24467 in QEventLoop::processEvents(unsigned)
> (this=0x82cd778, flags=4) at kernel/qeventloop_x11.cpp:311
> #21 0x40e94b6a in QEventLoop::enterLoop() (this=0x82cd778)
>     at kernel/qeventloop.cpp:191
> #22 0x40e94a86 in QEventLoop::exec() (this=0x82cd778)
>     at kernel/qeventloop.cpp:138
> #23 0x40e7a97f in QApplication::exec() (this=0xbffff570)
>     at kernel/qapplication.cpp:2471
> #24 0x081ccb8c in main ()
> #25 0x417674a2 in __libc_start_main () from /lib/libc.so.6
>
> Greetings,
> eva
> _______________________________________________
> KMail Developers mailing list
> kmail@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kmail

Sorry, forgot to mention, that I am talking about the KDE3_1_BRANCH here. I guess the 
argument that it will be released soon and that it crashes should be enough to have a look at 
the problem... 
 
Happy New Year, 
eva 

Closing, as those stability issue have since been improved and the crash is not 
reproducable. Eva, if you are still seeing it with kmail 1.5.3, please reopen it.