Comment 1 for bug 1810381

If malloc.c segfaults, it tries to allocate memory on a bad address. This can happen if either the Ram is faulty or a previous call previus call has corrupted the heap control structure.
I assume the error is unrelated to the current call in the stack trace.

Can you find a pattern that always crashes?
Did you do something special before the crash?