Well that is good news for the rest of us who can learn from all that you find out.
@ brett My hardware is currently be used in a demo so I cannot give a screenshot of the error but yes it was a OOM exception. I will it once I get it back.
When I first developed my code, I was running it on the TE35. Using that screen, I could allocate all windows in memory on startup and call them as needed. This resulted in a very quick interface especially with the screen animations.
However, when I tried this same procedure using the CP7, nothing worked. After running the debugger, I saw the OOM exception and did some reading through the forums as I mentioned before. So I switched the code to keep my one main window in memory and call the others as needed. In this particular case I am just loading a 17KB jpg image to demonstrate the resolution of the screen. If I dont call GC after I dispose of this window the OOM is generated. So to answer you question, I load only 2 windows at a time.
I did see the documentation on the allocating heap but then saw that it was changed in 4.2 and is no longer an API option???
However whether this is a stack issue or contiguous block issue, I cannot answer. How can I determine that?
Also if it is a stack issue as @ taylorza suggested, then is it possible or necessary to change the size of the custom heap?
Again thank you both for the input. Coming from the desktop it has been a long time since the Windows/DOS days where you needed to worry about memory and the 64K memory limits. I just need to remind myself of this constraint as I code in NETMF. But I bought the extra FLASH memory just in case