Fixed memory leak in DUnit’s TextTestRunner
Read OriginalThe article details a developer's experience fixing a long-standing memory leak in the DUnit unit testing framework's TextTestRunner. The leak was caused by calling Halt without freeing TTestResult and TTestSuite objects. The author provides the fix, discusses the abandoned state of DUnit, and briefly mentions a useful DUnit extension and the importance of enabling memory leak reporting.
0 comments
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
1
React vs Browser APIs (Mental Model)
Jivbcoop
•
3 votes
2
3
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister
•
2 votes
4
Using Browser Apis In React Practical Guide
Jivbcoop
•
1 votes
5
Better react-hook-form Smart Form Components
Maarten Hus
•
1 votes
6
Introducing RSC Explorer
Dan Abramov
•
1 votes
7
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz
•
1 votes