You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when declaring a py::enum<> adding values, all py objects create inside py::enum_<>::value() seems never destroyed.
I know that Python runtime have lot of leak, but it seems that py::class_<> doesn't generates leak, while enum_<> does.
Perhaps it's due to the usage of .attr() function inside enum_<>.
When embedding the interpreter inside a C++ program, is it something "normal" to have all values declare during py::enum_<>::value(...) never destroyed, or is it a pybind11 bug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
when declaring a py::enum<> adding values, all py objects create inside py::enum_<>::value() seems never destroyed.
I know that Python runtime have lot of leak, but it seems that py::class_<> doesn't generates leak, while enum_<> does.
Perhaps it's due to the usage of .attr() function inside enum_<>.
When embedding the interpreter inside a C++ program, is it something "normal" to have all values declare during py::enum_<>::value(...) never destroyed, or is it a pybind11 bug?
Beta Was this translation helpful? Give feedback.
All reactions