Is it due to basic misunderstandings of how memory is dynamically allocated and deallocated on the programmer’s part? Is it due to complacency?
Is it due to basic misunderstandings of how memory is dynamically allocated and deallocated
Share
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.
Is it due to basic misunderstandings of how memory is dynamically allocated and deallocated on the programmer’s part? Is it due to complacency?
No. It’s due to the sheer amount of accounting it takes to keep track of every memory allocation. Who is responsible for allocating the memory? Who is responsible for freeing it? Ensuring that you use the same API to allocate and free the memory, etc… Ensuring you catch every possible program flow and clean up in every situation(for example, ensure you clean up after you catch an error or exception). The list goes on…