I was using my Tungsten E simulator, and noticed that it has a 512k
heap setting already set when you download and run th esimulator. Is
that what is really is?
Here's the reason I ask. I noticed that my program I'm developing
crashes when running, and after stepping through it, I noticed that a
few of my memptrnew's were returning Null, so of course no more memory.
Now, I do create two offscreen buffers (hi-res), so I know I eat
through the memory prettyq uickly. Here's the deal...I ran
MemHeapFreeBytes(???) I think that is the name, and chose heap id's of
0, 1, and 2. Well, heap 0 is the one that I seem to be alllocating
memory from either by creating my offscreen buffer, or by using
memptrnew's.
But, when I looked at heap id 2, it had over 2 megabytes free (in the
simulator), and just wondering if I can go ahead and use that if I
want. Using MemChunkNew for instance, and specifying heap id. What is
strange, even a call to MemHandleNew doesn't even use anything from the
other heaps, why not?? Is this really 512k only on the Tungsten E, or
is that just an incorrect stock simulator setting.
Thanks!
|
