Comment # 1 on bug 929806 from Mel Gorman

Note that this probably indicates that the installer uses uninitialised memory.
The primary impact this patch has is that some new allocations that were filled
with zeros now contain uninitialised data. In older versions of glibc the
application would work by co-incidence. Reverting the patch avoids the problem
temporarily but it'll recur when glibc 2.22 is released if it's used by
openSUSE.

One way of testing would be to force the installer to globally set
MALLOC_CHECK_=2 during installation and see does that "fix" it. I don't know
how to setup a temporary installation environment like that but some of the
yast people should.