> From: cric[py]
>
> When I try to execute my application(wirte in appforge) in a Palm m105,
> ocacionally I get the follow error: MemoryMgr.c, Line 3036 Chunk
> over-Locked.
>
Palm has two ways to refer to a chunk of memory -- with a pointer, or with a
handle. When you have a handle, you have to lock it to get a pointer which
you can use to manipulate the memory, then unlock it when you are done
playing with it. Unlocked chunks of memory can be moved around by the OS to
make room for new memory allocations.
There is a finite number of times that a chunk of memory can be locked (I
think it's 14, but someone can correct me if I'm wrong.) So, what is
happening is that you are doing something to lock a particular handle more
than 14 times (without unlocking it in between) and finally, you get the
"chunk overlocked" error message.
I haven't used AppForge in a while, so I don't remember all of the ways in
which it might be locking memory chunks, but you should look for any code
that should occur in pairs (startsomething/endsomething,
locksomething/freesomething, etc.) and make sure you have included both
parts.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
