Good to know that you are trying to understand the internal qlikview mechanism. If i correct your question correctly then I would like to answer this.
The stack is always reserved in a LIFO order and heap is memory set aside for dynamic allocation.
Lets assume you have 1 gb of RAM then it will allocate the dynamic memory in heap.
Usually this does not happen it Qlikview.
All data resides in your server machine (RAM) for not only calendar generation but also for any other table, inline, qvd and database. whenever you load the data it resides in your RAM in compress format either on server side or client.
We also have a concept of Virtual Memory which is an ability to expand the database beyond your physical machine RAM.
(except heap and stack i assumed my address you correctly)
Thanks for your reply ... but i dont think it will used virtual memory..
B'coz it will all application will process in RAM and if it will flow from virtual to RAM memory
then it will require extra time to perform operation.
And Problem is still there How do we know that which memory used for different table generation and
auto table generation.