>If we bring this dialog up >15 times, the application crashes
>with a chunk overlocked crash.  I was able to track this down to the
>SysLibLoad call.

To help find out what is not being unlocked properly, try dumping the heap
(hd 0) and see what shows a steadily increasing lock count.  Or it could
actually be in the storage heap...


>It is my speculation that the SysLibLoad and SysLibRemove calls are
>correctly handling the handle for the shared library data
>thus causing this chunk overlock.  However, inspection of the library code
>does not corroborate this theory as the handle and resource
>gets and locks seem to be matched.

So you're saying you can't find the bug when you look at our source, but
are hoping it is in the OS and not in your app? :-)  Gee, thanks...

Dump the heaps and see what's going on.  Better still is to look at the
call chain when it crashes, to see what it is trying to lock when the count
gets to 15.

-David Fedor
Palm Developer Support


Reply via email to