On Wed, Mar 25, 2009 at 04:46:33PM +0000, corvid wrote:
Jorge wrote:
On Wed, Mar 25, 2009 at 04:20:19PM +0000, corvid wrote:
Jorge wrote:
- Removed a_Prefs_freeall because it was not used anywhere.
Should we rip out all of the *_freeall()s?
Ooops! It slipped.
The idea of those functions is to free memory there. They don't harm when empty. Let's keep them until something better springs up.
Should we add calls to them like in dillo1 and get them working, then?
Yes, that'd be good. Note that those functions are called at exit time. They were added long ago to help check for memory leaks. BTW, it'd be good to have some memory usage data for dillo-2.1. Something that can be put in a web page: e.g. a table with some explanations, on how dillo-2.1 compares with dillo-0.8.6 and with a big browser. IIRC sometime ago we made tests with a 13MB page, and the notion of dillo2 having near half the memory footprint of dillo1 came from there. We need to show some numbers and how we got them. Note: I remmeber having an awful memory footprint on 64bit Ubuntu. It didn't happen with 32bit. What's the current status, I don't know. -- Cheers Jorge.-