Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX

2012-07-08 Thread Joseph Tam
Timo Sirainen t...@iki.fi writes: #0 i_panic (format=0xff2302f8 Trying to allocate %u bytes) at failures.c:259 #1 0xff2068a4 in pool_alloconly_malloc (pool=0x60330, size=0) at mempool-alloconly.c:259 #2 0x00018248 in client_uidls_save (client=0x54d28) at

Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX

2012-07-08 Thread J E Lyon
On 8 Jul 2012, at 08:00, Joseph Tam wrote: Timo Sirainen t...@iki.fi writes: #0 i_panic (format=0xff2302f8 Trying to allocate %u bytes) at failures.c:259 Fixed: http://hg.dovecot.org/dovecot-2.1/rev/ea18b2ddb67b Date: Sat, 7 Jul 2012 05:52:03 +0300 2 hours after I reported it;

Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX

2012-07-08 Thread Timo Sirainen
On 8.7.2012, at 10.07, J E Lyon wrote: I think some of the things Timo does, he is able to do in his sleep . . What's annoying is that I sometimes do, and all the hard work gets lost somewhere to the dream world :(

Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX

2012-07-08 Thread Daniel Parthey
Timo Sirainen wrote: On 8.7.2012, at 10.07, J E Lyon wrote: I think some of the things Timo does, he is able to do in his sleep . . What's annoying is that I sometimes do, and all the hard work gets lost somewhere to the dream world :( Maybe it's just getting sorted out in your

[Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX

2012-07-06 Thread Joseph Tam
I noticed a bunch of crashes when Gmail users tried to slurp up their (empty) mailboxes. The problem is not noticed by clients though, but it crashes the pop3 process. POP3 session S: +OK Ready. C: USER user S: +OK C: PASS password S: +OK Logged in.

Re: [Dovecot] Dovecot 2.1.8 crashes when doing POP3 UIDL on empty INBOX

2012-07-06 Thread Timo Sirainen
On 7.7.2012, at 3.38, Joseph Tam wrote: #0 i_panic (format=0xff2302f8 Trying to allocate %u bytes) at failures.c:259 #1 0xff2068a4 in pool_alloconly_malloc (pool=0x60330, size=0) at mempool-alloconly.c:259 #2 0x00018248 in client_uidls_save (client=0x54d28) at