When reallocating a large amount of memory, Arrow is either triggering a bug in jemalloc or has a bug itself in the memory manager (many different applications reporting same issue but not clear from jemalloc issue description if they're sure it's in jemalloc or caused by other issues like using multiple memory allocation libraries in the same process, multithreaded access, etc).
Link to stack trace is here: https://gist.github.com/jeffknupp/73879feacf9c560afd4f1a20213dc6ef
Link to issue in jemalloc GitHub is here: https://github.com/jemalloc/jemalloc/issues/802
Originally observed in redis, discussed with jemalloc maintainer here: https://github.com/antirez/redis/issues/3799
This is entirely reproducible on Ubuntu 16.04 xenial, which uses version 3.6.0 according to `apt` metadata.