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
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
Container queries are rad AF!
Chris Ferdinandi
•
2 votes
3
Wagon’s algorithm in Python
John D. Cook
•
1 votes
4
An example conversation with Claude Code
Dumm Zeuch
•
1 votes
5
Top picks — 2026 January
Paweł Grzybek
•
1 votes
6
In Praise of –dry-run
Henrik Warne
•
1 votes