Re: Dovecot 2.3.0 imap-login using 100% CPU

On 10 Jan 2018, at 17.28, Jason Kiniry wrote: > > When in the process of testing out the 2.3.0 version of Dovecot, we noticed > that on a busy server, imap-login can sometimes take 100% CPU and remain > there indefinitely. We grabbed a gdb trace while it was happening: > >

Re: Dovecot 2.3.0 imap-login using 100% CPU

Is it possible for you to provide output of p *client p *client->next p *client->next->next until it hits NULL? Aki On 11.01.2018 01:29, Jason Kiniry wrote: > We were able to obtain a better backtrace: > > 0x7f4b303b5af5 in clients_notify_auth_connected () at > client-common-auth.c:839 >

Re: Dovecot 2.3.0 imap-login using 100% CPU

Thank you for this, we'll look into it. Aki On 11.01.2018 01:29, Jason Kiniry wrote: > We were able to obtain a better backtrace: > > 0x7f4b303b5af5 in clients_notify_auth_connected () at > client-common-auth.c:839 > 839 if (!client_does_custom_io(client) && >

Re: Dovecot 2.3.0 imap-login using 100% CPU

We were able to obtain a better backtrace: 0x7f4b303b5af5 in clients_notify_auth_connected () at client-common-auth.c:839 839 if (!client_does_custom_io(client) && client->input_blocked) { (gdb) run Thank you! Regards, Jason Kiniry > On Jan 10, 2018, at 4:28 PM,

Dovecot 2.3.0 imap-login using 100% CPU

When in the process of testing out the 2.3.0 version of Dovecot, we noticed that on a busy server, imap-login can sometimes take 100% CPU and remain there indefinitely. We grabbed a gdb trace while it was happening: dovenull 36053 31.2 0.0 60460 17316 ?R04:38 11:55