-
Notifications
You must be signed in to change notification settings - Fork 220
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
leak report #19
Comments
Generally, interpreter shutdown is a tricky business in Python, but collectable instances (including heap types) should be collected, and a lot of work has been put into this by the CPython team. This is needed to correctly close sockets, flush buffers, etc. -- things that are essential for the program to work correctly. However, a reference leak normally does not generate an error/warning and can still be missed. So when nanobind complains about things not being garbage collected, it deserves some scrutiny instead of disabling the warning. In your case, what seems to be responsible is a binary extension module of
This is as far as I got. |
I also encountered the leak issue rgl-epfl/cholespy#10 (comment). |
I filed a bug with Python: python/cpython#98253 |
Thanks for your kind reply! the |
Discussed in #13
Originally posted by tbrekalo March 31, 2022
How do I interpret the following?
Is it a bug on my part for getting something wrong in binding code or is it an issue with nanobind?
Side note: code causing this issue deals with shared pointers for another type that is not brought up by the error message.
Type 'Pile' is regular value type, I have a std::vector of them. So I am not sure how reference counting is being mentioned here.
Thanks for your help in advance.
Issue with false report of type leaks influenced by python type hints and imort of non-standard modules (in this case; seaborn 0.11)
The text was updated successfully, but these errors were encountered: