Re: dbghelp: Directly use Heap functions.

[Eric Pouech]

Markus Amsler a écrit :
> This reduces WoW debug symbol load time from about 100s to 18!
this also removes two key design features:
- memory is free:d (as Dimitry already pointed out)
- a memory pool is associated to every module, so that all allocations 
for a specific module are free:d when the module is unloaded

A+

-- 
Eric Pouech
"The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

dbghelp: Directly use Heap functions.

[Frank Richter]

On 30.04.2007 08:56, Eric Pouech wrote:
> Markus Amsler a écrit :
>> This reduces WoW debug symbol load time from about 100s to 18!
> this also removes two key design features:
> - memory is free:d (as Dimitry already pointed out)
> - a memory pool is associated to every module, so that all allocations
> for a specific module are free:d when the module is unloaded

If using the Heap* functions gives such a significant speed boost it may
make sense to create a heap with HeapCreate() per module and use that.
When a module is unloaded you can just call HeapDestroy() to get rid of
the memory allocated for that module.

-f.r.