Resources | Resources |



Releasing memory on SUSPEND

When a Brew application is suspended, it is important to release as much memory as possible. It is also important, however, to consider the location and layout of that memory. Even if the application only retains a few kilobytes, fragmentation may still be an issue. Applications should therefore ensure that any memory still needed while the application is suspended is either compacted and fragmentation-free or is managed as a movable memory block (discussed in Marking movable memory blocks).


All applications should implement this recommendation.