Just because you have no leaks, doesn't mean you don't still have a valid pointer or locked handle to a chunk in the middle of memory somewhere.
You might try the emulator debugger which allows you to view all the memory which your app has allocated, and see what changed between the first and subsequent task cycles. When you find it, make sure you allocate that chunk before your first task cycle so that it will be less likely to be allocated in the middle of the heap. >(as another note, I only see this on devices running 5 and below, 5.2 >devices work great.) Newer PalmOS models often have much larger dynamic heaps than some older models. IMHO. YMMV. Ron Nicholson HotPaw Productions http://www.hotpaw.com/rhn/palm ------ Original Message ------ On Mon, 26 Jan 2004 17:30:55, Fruber Malcome wrote: >In our application we do quite a lot with JPEG libraries and text that >creates and deletes many small chunks of memory. > >After a few iterations, it seems that there isn't enough memory to perform >the same task that was performed a few operations ago. >(e.g. decompress an image, then decompress another, then decompress the >original image etc.) > >After eliminating any possible memory leaks, I'm lead to the possible >conclusion that the memory must be fragmented, hence whey I run out of >memory. > >Is this a correct assumption? - Is there a way to verify it? - Is there a >way to fix it? > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
