Aryan PrajapatKnowledge Contributor
Whenever Python exits, why isn’t all the memory de-allocated?
Whenever Python exits, why isn’t all the memory de-allocated?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Questions | Answers | Discussions | Knowledge sharing | Communities & more.
1.Whenever Python exits, especially those Python modules which are having circular references to other objects or the objects that are referenced from the global namespaces are not always de-allocated or freed.
2.It is impossible to de-allocate those portions of memory that are reserved by the C library.
3.On exit, because of having its own efficient clean up mechanism, Python would try to de-allocate/destroy every other object.