I see the same block Andrew sees using vmmap and I wonder what buffer is attached to it.
Also vmmap reports a 4k block committed at 0x1F0000. If I ask vmmap to display free/unusable blocks,
it reports 0x1F1000 as unusable, size 60k and committed 60k. The problem is that the first block has been
allocated with 4k, so the next 60k are unusable. We should allocate by block by allocation granularity
as reported by GetSystemInfo().
We have been lucky (or maybe unlucky !) not being hit by this problem sooner.
Fabrice