Run each test in the unit test 100 times to see which step is missing, find the leaking place and fix it, and then cut off the person who developed this part
Troubleshoot the memory leak in the executed business. It may be that an array or data has not been released, or it may be caused by a wrong loop operation. Tools are generally very helpful in finding the problem. If you still can't find it, you can comment and execute the suspicious code in sections to determine it. . In the end, no matter who wrote the code in front of you, it won’t work if you scold him ten thousand times. After all, it’s already in your hands (wry smile).
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
There shouldn’t be a lot of leaks. It could be that a leak was called so many times that the leak was amplified.
Run each test in the unit test 100 times to see which step is missing, find the leaking place and fix it, and then cut off the person who developed this part
Troubleshoot the memory leak in the executed business. It may be that an array or data has not been released, or it may be caused by a wrong loop operation. Tools are generally very helpful in finding the problem. If you still can't find it, you can comment and execute the suspicious code in sections to determine it. .
In the end, no matter who wrote the code in front of you, it won’t work if you scold him ten thousand times. After all, it’s already in your hands (wry smile).
Redo... and then yell at the person before SB
Rage at the previous programmers and raise this number to 80,000+.
I choose a dog leash. . . .