[ https://issues.apache.org/jira/browse/ARROW-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102678#comment-16102678 ]
Jeff Knupp commented on ARROW-1282: ----------------------------------- It’s reproducible in 4.5.0 I’ve yet to test against 5.0 which was only released about a month ago, but I’m assuming it is also present in 0.4.4. I’ll try to install conda on one of our instances and test; the only issue is I’m using the dev version of pandas (which has my fix for the crashes that were happening on large columns) and I don’t have a lot of experience using condas, but I’ll do my best. > Large memory reallocation by Arrow causes hang in jemalloc > ---------------------------------------------------------- > > Key: ARROW-1282 > URL: https://issues.apache.org/jira/browse/ARROW-1282 > Project: Apache Arrow > Issue Type: Bug > Components: C++ > Reporter: Jeff Knupp > > 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.* -- This message was sent by Atlassian JIRA (v6.4.14#64029)