var user = { name: 'tom', age: 20, gender: 'male' } var test = document.getElementById('test'); test.onclick = function() { test.innerHTML = user.name; } user = null; // 释放对象I encountered an interview question like this recently. Is there any memory leak in this paragraph? If so, could you please tell me why and how to eliminate the memory leak?
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Memory leakSimply put, the allocated memory cannot be used or recycled until the browser process ends.
For the circular reference problemjust eliminate the reference directly, set the
test=null，因为jsgarbage collection mechanismto execute periodically, find out thevariablesthat are no longer used, and then release the memoryoccupied by them.Garbage collection
The principle is as shown in the picture below. Your test is elem in the picture. It refers to a dom element and adds an event handler to the dom element. However, the event processing function refers to the test in the external scope, so it is as follows: It becomes a circular reference.
What will appear to be a memory leak is actually the test rather than the user. Clearing the reference to the external test can destroy this circular reference.
In fact, these will not be a problem in modern browsers due to the use of the mark-sweep algorithm. In old browsers, the garbage collection algorithm will only cause memory leaks due to references, that is, the circular reference makes the object unavailable and cannot be garbage Recycle.
What is a memory leak?
This will cause an execution error. . . . . .
Definitely, it’s included in the CVTE interview questions. Because the reference to user.name is retained in the click event, it will still be leaked.
As for how to eliminate the problem, the only thing I can think of is to directly dereference it as mentioned above