On Thu, Mar 21, 2002 at 09:02:38PM +0200, Oded Arbel wrote: > Hmm. yes - I do compile using checking malloc. I re-comiled using native > malloc and it looks better - haven't had all the capacity testing done > on it yet though. Is it just that - checking malloc is so slow to cause > thrashing in code that do de-allocations ?
Hmm, this might be a bug in the checking malloc. It's not supposed to slow down when the number of allocations goes up. It only loops over all the allocated entries when it finds that a start marker has been damaged (which will be logged), or when gw_check_leaks() is called. Hmm, or if it encounters a pointer it considers "suspicious", there may be a bug there. Can we see the code you're using for measuring the List speed? Richard Braakman
