Great Refactor: Step 5: Remove all memory errors
Date: Monday, July 12 @ 10:17:08 CDT
Topic: The Great Refactor
We've come a LONG way since eMule 0.26d, when memory would leak at many megs an hour. Now you can run xMule for many hours without noticing much of an increase from the startup memory of 20MB. This will take it to the next level.
Memory warnings fixed: 21 out of 39
Memory leaks fixed: 0 out of 5
Initial run: 6664 errors from 43 contexts.
Modified at 9:44 (-5 UTC) on 12 July 2004
OK This is eaiser than I thought. Looks like we've done a really good job thus far :-)
Discovered memory leaks can be seen in real-time at
http://68.90.235.231/~HopeSeekr/memleaks.txt
|
|