Eschew global static object, to avoid issue with double-free #241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I was working on rapidsai/cuml#3316, I noticed that both libraries
libtreelite.so
andlibtreelite_runtime.so
contain a reference to the global static constanttypeinfo_table
. Since the constant was of typestd::unordered_map<std::string, std::string>
, it contains a non-trivial destructor. When both libraries are unloaded, both will attempt to simultaneously free the constanttypeinfo_table
from memory, leading to double-free and thus undefined behavior.Fix: Eliminate the use of global static constant and replace it with a function instead. Allocating memory in the local scope is safer and does not risk the possibility of double-free.