Yea it is. I appreciate it.
Ok, here's a question then.
After many Gremlins I see a lot of chunks that are unlocked (#0), owned by
my app (#2) and have 'fM' set on them, each of which is '0x64 requested
bytes' and actually '0x6c alloced bytes"
If I dump the memory they contain, it looks like menu items from various
menus in my application. Unfortunately, this list just keeps growing and
growing. This seems odd because although I do have a bunch of forms and
menus, the navigation between them is purely through FrmGotoForm and
FrmPopupForm coupled with FrmReturnToForm ... according to the docs, both of
these should handle the destruction of menus associated with each form. Yet,
it doesn't seem to be the case because I can see menu items leftover from
old forms when the app's on a completely different form...
Ben Combee <[EMAIL PROTECTED]> wrote in message
news:36410@palm-dev-forum...
>
> > Thanks for the info. Can you provide lock definitions?
> >
> > I see #0, #1, and #15 ...
> >
> > #15 = MemPtrNew
> > #0 = ??? <maybe globals??>
> > #1 = Forms data????
>
> No... #15 is the only special one -- the others are just the lock count --
a
> 0 means that the OS can move the chunk around, #1 through #14 mean that
its
> locked, and you need that many MemHandleUnlock calls to make it movable
> again.
>
> For the owner column, #2 is data your code has allocated. #0 and #1 are
> system allocated memory, but I'm not exactly sure why there are two
owners.
>
> Oh, the memory display in PalmDebugger is a little nicer, as it includes
> descriptions of a lot of the chunks -- I'm hoping that is implemented on
the
> Win32 version as well as the Mac.
>
> --
> Ben Combee
> Veriprise Wireless <http://www.veriprise.com>
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
