-
Notifications
You must be signed in to change notification settings - Fork 4k
ARROW-4702: [C++] Update dependency versions #4189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
40310b5 to
f13660f
Compare
wesm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from me. Were the issues you were seeing with jemalloc related to your build or something else? Would like for @xhochy to sign off on these changes since he's the most experienced with the jemalloc related stuff
|
The issues were because jemalloc now automatically overrides |
| "--with-jemalloc-prefix=je_arrow_" | ||
| "--with-private-namespace=je_arrow_private_" | ||
| "--without-export" | ||
| # Don't override operator new() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have an explanation why this is problematic or even an upstream issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My guess is that, when libarrow.so is used from external code, the external code will not get the operator new override. So if e.g. a Status is allocated inside libarrow.so and deleted by that external code, or vice-versa, you get one allocator trying to deallocate memory allocated by another allocator.
More generally, since Arrow is a library, it shouldn't muck with the default C and C++ allocators.
|
Facebook IIUC is a heavy user of operator new in their data structures (you can find it throughout https://github.com/facebook/folly) so it's not surprising that they would want to optimize it |
|
OK to merge this? |
No description provided.