To whom it may concern, in view of the discussion below may I suggest we remove the --with-gc option from the Dovecot default options?
Thanks.
Kind regards
Sebastian
> Anfang der weitergeleiteten Nachricht:
>
> Von: Sebastian Wolfgarten <sebast...@wolfgarten.com>
> Datum: 25. Oktober 2015 um 11:54:15 MEZ
> An: Timo Sirainen <t...@iki.fi>
> Kopie: dove...@dovecot.org
> Betreff: Aw: Memory leak or misconfiguration: Repeated allocation of very
> large block
>
> Hi Timo,
>
> alright, thanks I will recompile without gc - this is a standard build option
> on FreeBSD but I will get the port maintainer to maybe change this.
>
> Best regards
> Sebastian
>
>> Am 24.10.2015 um 23:19 schrieb Timo Sirainen <t...@iki.fi>:
>>
>> On 24 Oct 2015, at 14:59, Sebastian Wolfgarten <sebast...@wolfgarten.com>
>> wrote:
>>>
>>> Dear all,
>>>
>>> I am using Dovecot 2.2.19 and I keep on getting the following warnings in
>>> my mail.log file on FreeBSD 10:
>>>
>>> Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated
>>> allocation of very large block (appr. size 20480):
>>> Oct 24 10:45:28 server1 dovecot: imap: Error: May lead to memory leak
>>> and poor performance.
>>>
>>> I am wondering whether this is a configuration issue (i.e. a mistake in my
>>> current config) or whether I am hitting a bug. What’s the best way of
>>> figuring this one out? I tried increasing the verbosity of the logs but it
>>> did not really provide me with further information.
>>
>> I guess you have configured Dovecot --with-gc? I guess it's possible this is
>> a bug, but it could just as well be a false alarm. In general I don't
>> recommend/support --with-gc option (and I should probably just remove it
>> altogether). The easiest and the most usable way of finding memory leaks is
>> to run with valgrind (which must be done without-gc):
>>
>> service imap {
>> executable = /usr/bin/valgrind -q --show-reachable=yes --leak-check=full
>> /usr/libexec/dovecot/imap
>> }
>>
>> I'm not aware of any memory leaks right now.
>>
>
signature.asc
Description: Message signed with OpenPGP using GPGMail
