[Dovecot] imap processing spinning on the CPU
Version: 2.0.2 OS: Mac OS X 10.5.8
IMAP Client: Apple Mail.app on 10.5.8
Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get.
I know of one other person who is seeing this on a FreeBSD server (that person moved back to dovecot 1.2 which 'solved' the problem there).
I didn't notice anything in the list archive about this, but maybe I missed it.
(gdb) bt full #0 0x9534c2a8 in memchr () No symbol table info available. #1 0x001ef220 in parse_next_body_to_boundary () No symbol table info available. #2 0x001f02a8 in message_parser_parse_next_block () No symbol table info available. #3 0x0013c1cc in index_mail_cache_parse_continue () No symbol table info available. #4 0x0015c634 in mbox_save_body () No symbol table info available. #5 0x0015ca14 in mbox_save_continue () No symbol table info available. #6 0x000ecc58 in mail_storage_copy () No symbol table info available. #7 0x000f5b80 in mailbox_copy () No symbol table info available. #8 0x00003a10 in cmd_copy (cmd=0x80e820) at cmd-copy.c:66 search_ctx = (struct mail_search_context *) 0x403900 src_trans = (struct mailbox_transaction_context *) 0x403230 srcset_ctx = { str = 0x282d0, first_uid = 0, last_uid = 4294967295 } save_ctx = (struct mail_save_context *) 0x0 mail = (struct mail *) 0x81bc20 src_uidset = (string_t *) 0x282d0 copy_count_r = (unsigned int *) Cannot access memory at address 0x0
--
Daniel J. Luke
+========================================================+
| *---------------- dluke@geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
On 15.9.2010, at 21.59, Daniel J. Luke wrote:
Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get.
#1 0x001ef220 in parse_next_body_to_boundary () No symbol table info available. #2 0x001f02a8 in message_parser_parse_next_block ()
I'm pretty sure this is fixed by http://hg.dovecot.org/dovecot-2.0/rev/14a6e526900d .. I guess I should release 2.0.3 soon..
On Sep 15, 2010, at 5:16 PM, Timo Sirainen wrote:
On 15.9.2010, at 21.59, Daniel J. Luke wrote:
Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get.
#1 0x001ef220 in parse_next_body_to_boundary () No symbol table info available. #2 0x001f02a8 in message_parser_parse_next_block ()
I'm pretty sure this is fixed by http://hg.dovecot.org/dovecot-2.0/rev/14a6e526900d .. I guess I should release 2.0.3 soon..
Thanks, sorry I missed that patch. I'll get this deployed here (and hopefully on the FreeBSD system as well) and report back if it doesn't fix it.
--
Daniel J. Luke
+========================================================+
| *---------------- dluke@geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
On 9/15/2010 2:16 PM, Timo Sirainen wrote:
On 15.9.2010, at 21.59, Daniel J. Luke wrote:
Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get.
#1 0x001ef220 in parse_next_body_to_boundary () No symbol table info available. #2 0x001f02a8 in message_parser_parse_next_block () I'm pretty sure this is fixed by http://hg.dovecot.org/dovecot-2.0/rev/14a6e526900d .. I guess I should release 2.0.3 soon..
I'm seeing the same thing. I went back to 2.01 for now.
participants (3)
-
Daniel J. Luke
-
Marc Perkel
-
Timo Sirainen