Re: heap
In practical terms, pretty much any program under WinXP would
load a DLL at 0x20000000 (xptheme.dll) thus cutting .25 GB
address space. Most system DLLs are loaded in the 0x7xxxxxxx
address space, but some are loaded in 0x6xxxxxxx and even in
0x5xxxxxxx. That cuts another 0.25 to 0.375GB chunk of
addresses. So 2GB - 0.25 - 0.375 = 1.375 GB of potential
continuous addresses. Add to that other heaps allocated by the
process itself (which may or may not use some of this space,
since they may fit under 0x20000000). Thread stacks typically
will be allocated in lower addresses due to small sizes, however.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Nathan Mates" <nathan@visi.com> wrote in message
news:13jp1cc1osb9o11@corp.supernews.com...
In article <A15C56B4-443B-4DDB-805B-6FB67B5794F8@microsoft.com>,
=?Utf-8?B?R2Vvcmdl?= <George@discussions.microsoft.com> wrote:
After reading your comments, I am clear now. I want to confirm with
you that you mean the total size of all the heaps (including the
default heap and other additional allocated private heaps) allocated
by a process can not exceed the limitation (e.g. 2G) of the
OS. Right?
Go back and re-read my post (the grandparent to this
one). Specifically, the part where I list out all the various things
that count against the per-process limit imposed by the OS. You're
going to find that devil is in the details, and that the ideal
situation is reached ... *never*. You've got to account for at least a
10% tax on your address space. Minimum.
Nathan Mates
--
<*> Nathan Mates - personal webpage http://www.visi.com/~nathan/
# Programmer at Pandemic Studios -- http://www.pandemicstudios.com/
# NOT speaking for Pandemic Studios. "Care not what the neighbors
# think. What are the facts, and to how many decimal places?" -R.A.
Heinlein