Date: Tue, 23 Sep 2014 03:10:16 +0400 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: freebsd-stable@FreeBSD.org Cc: freebsd-toolchain@freebsd.org, Dimitry Andric <dim@FreeBSD.org> Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140922231016.GA1301@hades.panopticon> In-Reply-To: <20140228154328.GA13454@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <E5857DB5-65CE-4A55-9DF4-B82B86EA7DBB@FreeBSD.org> <20140228154328.GA13454@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
* Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > > > I've been getting some failure mails from pkg building cluster related > > > to clang crashes: > > > > > > http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s/logs/arx-libertatis-1.0.3_2.log > > > http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/logs/supertuxkart-0.8.1.log > > > > > > At first I thought they'll go away with clang 3.4, but recently I've > > > added HEAD jail to my tinderbox and reproduced these. Also a reason > > > of crashes become apparent: c++ eats all available memoty (15G RSS > > > in my case). > > > > > > I though of investigating these further, but wanted to check if it's > > > already known first. > > > > There are a few known OOM bugs in 3.4, but from the logs it is not > > immediately apparent if you are hitting those, or if they are new bugs. > > Note that it affects both 3.3 and 3.4. I think it was triggered by > something unrelated to clang update, maybe libc++ update. > > > To be able to figure that out, we need the files mentioned in clang's > > diagnostic messages, e.g. for arx-libertatis: > > > > /tmp/Input-XkKTNq.cpp > > /tmp/Input-XkKTNq.sh > > Here's one from arx-libertatis: > > http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 > > The bug is reproducible on my 10.x with both system clang 3.3 (after > removing -vectorize-loops -vectorize-slp options) and with clang 3.4 > from ports. I'll just remind that this is still an issue, and it's getting into 10.1. Could we maybe disable compiler features with lead to these crashes? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140922231016.GA1301>