
11-17-2008, 05:28 PM
|
| | Forums Moderator Device(s): 9000 Carrier: O2 | | Location: UK Join Date: Aug 2008 Posts: 4,328 Likes Received: 279
Thanked 305 Times in 185 Posts
| |
Facebook and Viigo both have many user reports here for memory leaking.
Closing the application won't always resolve the losses due to a memory leak. The general concept is that if a process requests memory allocation the owner (same process) *must* release the allocation when it is no longer required - and in any case immediately before the parent app terminates. Other applications are not allowed to touch the allocated memory. If this release fails an orphan block of addresses will be marked as 'used'. The memory manager should respect that allocation even if the app is closed, and the block will be skipped by garbage collection and never returned to pool. Next time you open the app it does the same trick again, and another block is marked, and another, and....
Last edited by branta; 11-17-2008 at 05:32 PM.
|