Date: Sun, 25 Oct 2015 11:55:42 +0100 From: Sebastian Wolfgarten <sebastian@wolfgarten.com> To: ports@freebsd.org Subject: Fwd: Memory leak or misconfiguration: Repeated allocation of very large block Message-ID: <7FBFC8D1-EE93-4F14-8A7B-60DA1078F4E2@wolfgarten.com> References: <EE8AB981-E079-4A35-8138-D04B48525B6A@wolfgarten.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_302E21D2-8453-4F9F-B2D2-C6F25C6920F9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
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:
>=20
> Von: Sebastian Wolfgarten <sebastian@wolfgarten.com>
> Datum: 25. Oktober 2015 um 11:54:15 MEZ
> An: Timo Sirainen <tss@iki.fi>
> Kopie: dovecot@dovecot.org
> Betreff: Aw: Memory leak or misconfiguration: Repeated allocation of =
very large block
>=20
> Hi Timo,
>=20
> 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.
>=20
> Best regards
> Sebastian
>=20
>> Am 24.10.2015 um 23:19 schrieb Timo Sirainen <tss@iki.fi>:
>>=20
>> On 24 Oct 2015, at 14:59, Sebastian Wolfgarten =
<sebastian@wolfgarten.com> wrote:
>>>=20
>>> Dear all,
>>>=20
>>> I am using Dovecot 2.2.19 and I keep on getting the following =
warnings in my mail.log file on FreeBSD 10:
>>>=20
>>> 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.
>>>=20
>>> 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=E2=80=99s 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.
>>=20
>> 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):
>>=20
>> service imap {
>> executable =3D /usr/bin/valgrind -q --show-reachable=3Dyes =
--leak-check=3Dfull /usr/libexec/dovecot/imap
>> }
>>=20
>> I'm not aware of any memory leaks right now.
>>=20
>=20
--Apple-Mail=_302E21D2-8453-4F9F-B2D2-C6F25C6920F9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJWLLUuAAoJEKIH+IvLUCrDPR8P/ip970Xs+1oXOQZG48GuPemc
tyaUWn9fhTZnRwzGmNQIeQB0JS39gWBNziuKsl+AD/dFcVR1iKLz84ae/EznnDMX
YLtw2Uw8jqaEJlytEwSOQay/xRm6yLT8ZHDCIBSG0kHd25xGle16AyyKNKA4kVaj
XuRRg5ymazWLMK3ocZy7ktJQ8w3SYBK0kletaDW+ExA7yBZ5jsSxI0pSidRRvAZw
OrQU0avmEX3v9FTvWgEWURWC/3GzeBElhS4DC09ksqd6V9M0pJnnAwHrChvOo666
QzHyM1eQjD+9hrXjZS5ZlAGSYPC2PSa+VbNQMa/aomwm/hdf4CQEnERFYPrPnq8L
ac9150cAWZDmdVuSik4k1r8eqbMIeD+iKOWQGcAEfqo9Zhj6zciHt3AwFOxETpV7
rlHo/R5p+9F3tpEgxESa5iV18ebtqjlfNWHQjZWtKrg5XyQm5YY6PABsX39wSove
tVsJ1M08y0UPU6NeOcJa58rRjyT0pRMezR5K79VncoopDRjuAPe7eXj1abAWnP40
KxB3VLdZvRaq3onN6Cp8TE9/vwd/mwIhjzhugJgqJbak45pSnfGJdq9TbFOnYBkg
FYY/tJoK87V0z3v4Pg8UjIHRuQdfYhrRj3j1KLqe8JzkWcb3+neKqUngcGnPLEeg
RDOUKB2MoeX4nX8vm2Xg
=Ofng
-----END PGP SIGNATURE-----
--Apple-Mail=_302E21D2-8453-4F9F-B2D2-C6F25C6920F9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7FBFC8D1-EE93-4F14-8A7B-60DA1078F4E2>