Fwd: Memory leak or misconfiguration: Repeated allocation of very large block

[Jason Unovitch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On December 5, 2015 6:43:55 AM EST, Sebastian Wolfgarten <sebastian at wolfgarten.com> wrote:
>Any views on this?
>
>> Anfang der weitergeleiteten Nachricht:
>>
>> Von: Sebastian Wolfgarten <sebastian at wolfgarten.com>
>> Datum: 25. Oktober 2015 um 11:55:42 MEZ
>> An: ports at freebsd.org
>> Betreff: Wtr: Memory leak or misconfiguration: Repeated allocation of
>very large block
>>
>> 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 <sebastian at wolfgarten.com
><mailto:sebastian at wolfgarten.com>>
>>> Datum: 25. Oktober 2015 um 11:54:15 MEZ
>>> An: Timo Sirainen <tss at iki.fi <mailto:tss at iki.fi>>
>>> Kopie: dovecot at dovecot.org <mailto:dovecot at 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 <tss at iki.fi
><mailto:tss at iki.fi>>:
>>>>
>>>> On 24 Oct 2015, at 14:59, Sebastian Wolfgarten
><sebastian at wolfgarten.com <mailto:sebastian at 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.
>>>>
>>>
>>

Have you filed a PR for the issue and/or reported this to the mail/dovecot2 maintainer?
-----BEGIN PGP SIGNATURE-----

iQFHBAEBCgAxKhxKYXNvbiBVbm92aXRjaCA8amFzb24udW5vdml0Y2hAZ21haWwu
Y29tPgUCVmcNXAAKCRBv1JwwFhyqbuCBB/0Yqw6Bhecsegznzx21WxZD+aJzd9k5
8OPUT3VbTtkK33BKgozZYFzEW0+9XSdU6vK+AreuBcWAtMb34F5W6H3uqfezv0by
HvdftdIbUao1TYUhGlDL21k1PaNNPpfoDkqpTTV0eEAuM0p3ZZP3YWwWSXGzmvgu
KGZKdx3SF/oy6Ut2DHYZIj5JQVBd20wZrFtKt6/orudn12eFEfWcB9fTqQ1ESJBf
Q1Ue2zsPUQn7AcbP/UW99CdgV+BTM5rI7yZu8ohnJWj0rimSmWMWY5cqbzbBkTem
hBRdJ+KMD0SpdOHw7zGMHKN+MHLWCBl+4ZmIUxOEPbolLoljAdvbTt4i
=FN+e
-----END PGP SIGNATURE-----