At 10:17 PM 5/29/2003 +0300, iyad abu-shaera wrote:
Am doing a project that contains about 50 forms,

50 forms? Wow ... sanity check: are you sure Palm is an appropriate platform for such a UI-intensive application? Case in point: I was retained to develop a prescription writing system a while back, and their UI guy had mocked up about 30-40 different forms he wanted me to implement. The first thing I did was to work this down to four forms. Keeping track of the UI flow and state information across that many forms becomes intractable.


and it is a data-driven project. Also there is many rules that will validate the data that entered by the user.. Am afraid from the memory leak.. so if there is a way to refresh the memory to remove the fragments and any unused memory chunks.


My advice is to stop everything and track down the memory leak and fix it. Do this by running your app on the Palm OS Emulator (POSE) loaded up with a debug ROM. POSE will report leaked memory as soon as you exit your app. So start the app, and exit right away -- if it reports leaked memory, you have narrowed the leak down to happening on the first form (or in AppStart() etc). If no leaks are reported, start up the app, advance into a second form, and then exit. If it reports leaked memory, you have narrowed it down to the second form. etc, etc.


Also if there is a way that I can stop and remove every thing from the memory and return back, for me it is ok..


If you really don't have time to track down the memory leak, you can issue a soft reset to reclaim leaked memory via SysReset(). You can tell when memory is getting dangerously low by calling MemHeapFreeBytes().

-Jeff Ishaq


-- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/

Reply via email to