2 Oct
2004
2 Oct
'04
6:31 p.m.
From: Hartmut Birr
I've still more problems with the modifications in the
virtual memory functions. My test case is ctm from rosapps.
It shows the cpu time and memory usage of the processes.
While waiting for a keyboard event, ctm
(kernel32) destroys and creates every 100ms a new thread. It
seems, that the memory (teb, stack, ...) isn't freed. The
thread itself is destroyed. Ps
shows always two threads for ctm.
Ok, I'll dig into it to see what's wrong. Is this causing you major problems
(i.e. should I rollback the changes for now)?
The reason for the changes is that the Windows Installer (instmsiw.exe)
depends on VirtualAlloc() returning 64k aligned blocks. There are other
sources (e.g.
http://blogs.msdn.com/oldnewthing/archive/2003/10/08/55239.aspx) that
indicate that VirtualAlloc really should return 64k aligned blocks.
Ge van Geldorp.