Even if the MemHandleLock() calls are matched by MemHandleUnlock()
calls, if these calls are in different routines the program flow may go
through
one routine more often than the other ... perhaps due to unanticipated
events.
Try incrementing a counter (use the feature manager) where the lock occurs,
and decrementing it where the unlock occurs. Then write a second app
to display the value of that counter. Run your program a couple of times
then check the value.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
[EMAIL PROTECTED] wrote in message <[EMAIL PROTECTED]>...
>
>
>
>Me too. I checked to make sure there is a MemHandleUnlock() to each
>MemHandleLock(). I also close all open databases and forms in AppStop().
There
>is no problem to debug the first time, but why the subsequent times.
>
>static void AppStop(void)
>{
> FrmCloseAllForms();
> if (gFacilityDB)
> DmCloseDatabase(gFacilityDB);
> if (gAddressDB)
> DmCloseDatabase(gAddressDB);
> if (gContactDB)
> DmCloseDatabase(gContactDB);
> if (gFrpDB)
> DmCloseDatabase(gFrpDB);
>}
>
>
>-Elizabeth
>
>
>
>|--------+------------------------>
>| | [EMAIL PROTECTED]|
>| | ntmail.com |
>| | |
>| | 08/03/00 12:08|
>| | PM |
>| | Please respond|
>| | to |
>| | palm-dev-forum|
>| | |
>|--------+------------------------>
> >-----------------------------------------------------------|
> | |
> | To: [email protected] |
> | cc: |
> | Subject: Chunk-Over Lock Error upon launch |
> >-----------------------------------------------------------|
>
>
>
>
>
>Hello,
>
>First off in lue of the many weird post recently I will first qualify my
>question, I have RTFM. So that
>being said, my problem is as follows:
>
>My app runs normally and displays no errors while executing, however if the
>app is stopped and started
>maybe four or five times (number seems to vary) on launch the OS will
report
>a "Chunk-Over Locked" error and the device requires a reset. I can not
>get the emulator to replicate this nor does it indicate any memory errors.
>I recently read a post about a chap who had a problem similar to this and
>the solutions for him was to call "FrmCloseAll" upon exit of the app. I
>have included this as the last action I do before the app exits; however I
>still have this problem. Can any body shed any light on how to trace this
>Over locked chunk down. I can say that every call to MemLock has a
>corresponding MemUnlock. There must be some From function that is locking
>the memory and I just don't know I'm supposed to Unlock it manually? Also
>I know there is a way to use the hd0 debugging function however I have not
>been able to find any documentation on it.
>
>Thanks,
>Jason Simpkins
>
>
>
>--
>For information on using the Palm Developer Forums, or to unsubscribe,
please
>see http://www.palmos.com/dev/tech/support/forums/
>
>
>
>
>
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
