Note that other stuff can also cut into your dynamic heap, such as the Network stack, OS updates and Hackmaster extensions. Unless you can test against every possible combination of Network connections, future OS updates and all possible Hacks, then using the Debug ROMS to simulate low memory situations seems like a sensible idea. If you think the 3.5 Debug ROMs might be too conservative, you might at least test with an extra orphan 40k chunk of memory lying around in the middle of the dynamic heap (simulating networking plus some). Ron Nicholson HotPaw http://www.hotpaw.com/rhn/hotpaw/ - Mike Davis writes: >So, what I want to do is characterize the >operation of this application and see if I must worry about the >problem. > >First, I have tested the application with the Emulator and release >ROMS and never see a problem. > >Second, I have tested this on a PalmIIIc and PalmIII (4 MEG) and >don't see any problems. > >Third, I have tested this on 2MEG devices with the Emulator and don't >see a problem. Except with 3.5 Debug ROM. > >Only with the 3.5 Debug ROM do I noitce the problem. I know this is >by design. > >So, if my app seems to work with all of these cases, is it likely >that I can get away from having to handle the FrmUpdateForm event? > >Will this application likely continue to work? > >If not, what can change to cause me to eventually NOT work on a >device? -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
