Fix destruction order problem in getCoreAllocator
authorGiuseppe Ottaviano <ott@fb.com>
Wed, 7 Jun 2017 00:32:12 +0000 (17:32 -0700)
committerFacebook Github Bot <facebook-github-bot@users.noreply.github.com>
Wed, 7 Jun 2017 00:35:42 +0000 (17:35 -0700)
commit55791684950381d92cef305d1e9124120b178ad5
treeaf5502ce86dd84867735c0385a67621f244f7b89
parent03c1142df9b0ddd450430b7aae70940c0d071ff6
Fix destruction order problem in getCoreAllocator

Summary: We cannot guarantee the correct destruction order of the Meyers singleton owning the allocator, and the objects allocated with it, so we just leak it using `Indestructible`.

Reviewed By: djwatson

Differential Revision: D5196227

fbshipit-source-id: ec07ab1e21af7814194883b252d45aa36d2a04b1
folly/detail/CacheLocality.h