Mon premier blog

Garbage Collection: Algorithms for Automatic Dynamic Memory Management Rafael D Lins, Richard Jones
Publisher: Wiley

Nevertheless, all of the commonly used JVMs have garbage collectors, and most garbage collectors use similar algorithms to manage their memory and perform collection operations. Garbage Collection does exactly what it's more fancier name “Automatic dynamic memory management” suggests. Old space is still collected by one thread. Nor does it specify how a garbage collector should work. There is a delete operator in Flex, but it's only for freeing dynamic properties, not for deleting objects. You probably heard, read or even learned that Flex was managing the memory automatically for you, does it mean you don't have any responsibility regarding memory management in Flex? As I discussed in my last post on Memory Allocation dynamic memory is hard to manage One of the duty of a GC system is to automate this process by tracking down (using various algorithms) such objects and reclaim the memory used by them automatically. This is a special mode of parallel scavenge collector in which it can dynamically adjust configuration of young space to adapt for an application. Garbage Collection: Algorithms for Automatic Dynamic Memory Management by Richard Jones, Rafael Lins - Find this book online from $26.99. Java (and dominating majority of other modern languages) features automatic memory management aka garbage collection. Memory management in Flex using garbage collection, responsibilities it puts on developers, classical causes of memory leaks and good practices to avoid them. Once instance of object becomes Parallel scavenge GC mode is using parallel implementation of young collection algorithm.