Summary: | IMAP resources sometimes crashes (or: random crashes on akonadi resources). | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Ildefonso Camargo <icamargo> |
Component: | IMAP resource | Assignee: | Christian Mollekopf <chrigi_1> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bruno, gtdev, kdepim-bugs, mollekopf, vkrause |
Priority: | NOR | Keywords: | triaged |
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Ildefonso Camargo
2012-03-19 00:18:40 UTC
Created attachment 73286 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.9) on KDE Platform 4.9.00 using Qt 4.8.1
- What I was doing when the application crashed:
Same situation with two accounts. One IMAP resourse still crash on KDE 4.9.0
-- Backtrace (Reduced):
#6 check_parent_thread (currentThreadData=<optimized out>, parentThreadData=<optimized out>, parent=0x14b0290) at kernel/qobject.cpp:696
#7 check_parent_thread (parent=0x14b0290, parentThreadData=<optimized out>, currentThreadData=<optimized out>) at kernel/qobject.cpp:685
#8 0x00007f75c0f612f7 in QObject::QObject (this=0x1591e70, parent=0x14b0290) at kernel/qobject.cpp:729
#9 0x00007f75bde18bb6 in KJob::KJob (this=0x1591e70, parent=<optimized out>) at ../../kdecore/jobs/kjob.cpp:50
#10 0x00007f75bfb63b1d in KIMAP::Job::Job (this=0x1591e70, dd=...) at ../../kimap/job.cpp:37
After starting from a blank home, with kde4.10 I use akonadi on external pg (9.2) and 11 imap offline account I'm getting new message and segfault of postgresql 013-01-30 10:33:19 CET LOG: server process (PID 3525) was terminated by signal 11: Segmentation fault 2013-01-30 10:33:19 CET DETAIL: Failed process was running: EXECUTE qpsqlpstmt_ef (197) 2013-01-30 10:33:19 CET LOG: terminating any other active server processes 2013-01-30 10:33:19 CET bf_akonadi bf_akonadi WARNING: terminating connection because of crash of another server process 2013-01-30 10:33:19 CET bf_akonadi bf_akonadi DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2013-01-30 10:33:19 CET bf_akonadi bf_akonadi HINT: In a moment you should be able to reconnect to the database and repeat your command. 2013-01-30 10:33:19 CET bf_akonadi bf_akonadi WARNING: terminating connection because of crash of another server process 2013-01-30 10:33:19 CET bf_akonadi bf_akonadi DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. cat postgresql-2013-01-30_133734.log 2013-01-30 13:37:34 CET LOG: database system was shut down at 2013-01-30 13:37:33 CET 2013-01-30 13:37:34 CET LOG: database system is ready to accept connections 2013-01-30 13:37:34 CET LOG: autovacuum launcher started 2013-01-30 14:54:04 CET bf_akonadi bf_akonadi ERROR: compressed data is corrupt 2013-01-30 14:54:04 CET bf_akonadi bf_akonadi STATEMENT: EXECUTE qpsqlpstmt_10d (407042, 'PLD:HEAD') The postgresql server is used for geographic & statistics treatment (heavy load but not when akonadi was working) and didn't segfault ? Trying to backup the data on a full new setup. psql -d bf_akonadi -c "\COPY public.parttable (id, pimitemid, name, data, datasize, version, external) TO parttable.copy" What could explain this ? happening twice in less than two weeks. ps : other database work just great ( even those with billions records ) *** Bug 322400 has been marked as a duplicate of this bug. *** The IMAP resource has a new maintainer, reassigning to him. Does this still apply to >=4.11.3? Looks like a threading related crash, of which many have been fixed meanwhile. I've not seen those trouble actually with running 4.11.3 and postgresql 9.2.4 and the \copy command work not perfectly. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |