Hi, I have a very wierd situation on code that has been working fine on OS4 and OS5.0 (T1). This little gem (being memory related ) is wonderfully transient but after loading up production code with lots of traces it looks increasingly like MemHandleUnlock calls are "sometimes" completing successfully but leaving handles locked. Specifically this is biting me when I am trying to expand records (Unlock, Resize, Lock). I have only been able to reproduce the errors my users are seeing by forcing extra (un-unlocked) locks on the handle before I start this sequence.
Has anyone seen anything like this? thanks Andrew Waites Just4Markets Pty Ltd -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
