| Summary: | akonadi imap resource crash (segfault) when trying to sync after DNS went away | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] Akonadi | Reporter: | Sven Eden <sven> |
| Component: | IMAP resource | Assignee: | Kevin Ottens <ervin> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dreibh, gapon007, jaript, kdepim-bugs, mail, vkrause |
| Priority: | NOR | ||
| Version: | 4.7 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Sven Eden
2011-09-15 11:55:24 UTC
I will need more information for that one, namely the mail server used. Also to debug that kind of cases efficiently, I'd need to be provided with some idea of the IMAP traffic which created the issue. That can be done by setting the KIMAP_LOGFILE environment variable and restarting the akonadiserver. For instance: export KIMAP_LOGFILE=imaplog akonadictl restart Look at the pid of the imap resource you should then have a couple of imaplog.pid.* files. Wait for the crash, and then provide me what happened before the crash. It's the best way for me to create a test case that I can reproduce here. Only caveat though is that some private data is likely in the log (except the authentication phase, after that it logs everything) so you'd have to trust me with your data and send it privately. It's the old companies mail server, using squirrel if I am not mistaken. I'll look into it on Monday. I _hope_ I can reproduce the error by simply altering /etc/resolv.conf to something unresponsive, but that's a shot in the dark. I have never - in over three years - seen the dns servers going down, but maybe it works out that way. *** Bug 283581 has been marked as a duplicate of this bug. *** Created attachment 64373 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
→ Suspended my notebook
→ Resumed while being offline (at the train)
→ After ~15 minutes, the IMAP resource crashed
Not sure about the used mailserver, very likely Dovecot.
Couldn't reproduce it so far to generate more debug information.
-- Backtrace (Reduced):
#6 _wordcopy_fwd_aligned (dstp=<value optimized out>, srcp=<value optimized out>, len=2305843009213345392) at wordcopy.c:118
#7 0x00007f1cf23a61c8 in memmove (dest=0xa6e348, src=<value optimized out>, len=18446744073709551608) at memmove.c:73
#8 0x00007f1cf5c6882c in QListData::remove (this=0x8283e8, i=<value optimized out>) at /usr/include/bits/string3.h:58
#9 0x00007f1cf5c68861 in QListData::erase (this=0xd16fb8, xi=<value optimized out>) at tools/qlist.cpp:412
#10 0x000000000044f703 in erase (this=0x8283a0, session=0x853740) at /usr/include/qt4/QtCore/qlist.h:453
*** Bug 283764 has been marked as a duplicate of this bug. *** *** Bug 282598 has been marked as a duplicate of this bug. *** Note: If your bug was marked as a duplicate of this one, please read the comment #1. Created attachment 64459 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
It happened here again, when the gateway was temporarily out of service.
Unfortunately I didn't have Akonadi started manually to generate detailed log information at this time, but I think the backtrace looks a little different this time and therefore probably provides additional helpful information.
-- Backtrace (Reduced):
#6 _wordcopy_fwd_aligned (dstp=<value optimized out>, srcp=<value optimized out>, len=2305843009213617696) at wordcopy.c:109
#7 0x00007f3d9bfed1c8 in memmove (dest=0xab40e0, src=<value optimized out>, len=18446744073709551608) at memmove.c:73
#8 0x00007f3d9f8af82c in QListData::remove (this=0x83c668, i=<value optimized out>) at /usr/include/bits/string3.h:58
#9 0x00007f3d9f8af861 in QListData::erase (this=0xb48fd0, xi=<value optimized out>) at tools/qlist.cpp:412
#10 0x000000000044f703 in erase (this=0x83c620, session=0x8e3e60) at /usr/include/qt4/QtCore/qlist.h:453
Created attachment 64527 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
It happened again. This time I was able to get the IMAP debug log, which I sent now privately to Kevin Ottens.
-- Backtrace (Reduced):
#6 _wordcopy_fwd_aligned (dstp=<value optimized out>, srcp=<value optimized out>, len=2305843009213281472) at wordcopy.c:106
#7 0x00007f212055e1c8 in memmove (dest=0x8705e8, src=<value optimized out>, len=18446744073709551608) at memmove.c:73
#8 0x00007f2123e2082c in QListData::remove (this=0x881368, i=<value optimized out>) at /usr/include/bits/string3.h:58
#9 0x00007f2123e20861 in QListData::erase (this=0xb95fd8, xi=<value optimized out>) at tools/qlist.cpp:412
#10 0x000000000044f703 in erase (this=0x881320, session=0xaa6480) at /usr/include/qt4/QtCore/qlist.h:453
Created attachment 64576 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.2
- What I was doing when the application crashed:
It happened again. I think I missed some logfiles last time, so I sent all related current logfiles again to Kevin Ottens privately.
-- Backtrace (Reduced):
#6 _wordcopy_fwd_aligned (dstp=<value optimized out>, srcp=<value optimized out>, len=2305843009213410456) at wordcopy.c:112
#7 0x00007f587d3fe1c8 in memmove (dest=0xa55498, src=<value optimized out>, len=18446744073709551608) at memmove.c:73
#8 0x00007f5880cc082c in QListData::remove (this=0x81bea8, i=<value optimized out>) at /usr/include/bits/string3.h:58
#9 0x00007f5880cc0861 in QListData::erase (this=0xc7efc8, xi=<value optimized out>) at tools/qlist.cpp:412
#10 0x000000000044f703 in erase (this=0x81be60, session=0x7f43e0) at /usr/include/qt4/QtCore/qlist.h:453
Created attachment 64842 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
Program has crashed while synchronizing e-mails over unreliable Internet connection (via UMTS on moving train).
-- Backtrace (Reduced):
#6 __memmove_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2819
#7 0x00007fbb8c7098b9 in QListData::remove (this=0xaca378, i=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:58
#8 0x00007fbb8c709b9b in QListData::erase (this=0xaca378, xi=<optimized out>) at tools/qlist.cpp:412
#9 0x0000000000454595 in erase (it=<optimized out>, this=<optimized out>) at /usr/include/qt4/QtCore/qlist.h:453
#10 removeFirst (this=0xaca378) at /usr/include/qt4/QtCore/qlist.h:273
Created attachment 64843 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.7) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
Program has crashed while synchronizing e-mails over unreliable Internet connection (via UMTS on moving train).
-- Backtrace (Reduced):
#6 __memmove_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2819
#7 0x00007fbb8c7098b9 in QListData::remove (this=0xaca378, i=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:58
#8 0x00007fbb8c709b9b in QListData::erase (this=0xaca378, xi=<optimized out>) at tools/qlist.cpp:412
#9 0x0000000000454595 in erase (it=<optimized out>, this=<optimized out>) at /usr/include/qt4/QtCore/qlist.h:453
#10 removeFirst (this=0xaca378) at /usr/include/qt4/QtCore/qlist.h:273
OK, it's now likely fixed by all the commits gone into the direction of handling connection losses better. Please test again with 4.8.1 when it will be out and reopen if it still shows up. I just tried to have kmail (4.8.0) to crash again, but couldn't reproduce. I changed the nameserver entry in /etc/resolv.conf to something non-existant and fetched mails. I get a message that the pop3 server is not available, but the imap account simply stays silent. No crash anymore! *yay* |