Garbage collection (computer science) | Wikipedia audio article
Channel: wikipedia tts
Date: 2018-12-31

This is an audio version of the Wikipedia Article:
https://en.wikipedia.org/wiki/Garbage_collection_(computer_science)


00:02:00 1 Principles
00:03:43 1.1 Advantages
00:04:56 1.2 Disadvantages
00:07:44 2 Strategies
00:07:53 2.1 Tracing
00:08:39 2.2 Reference counting
00:14:50 2.3 Escape analysis
00:15:32 3 Availability
00:16:42 3.1 BASIC
00:18:07 3.2 Objective-C
00:19:06 3.3 Limited environments
00:19:43 3.4 Garbage Collectors for JDK
00:20:11 3.5 Compile-time use
00:20:47 3.6 Real-time systems
00:22:26 4 See also



Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

Listen on Google Assistant through Extra Audio:
https://assistant.google.com/services/invoke/uid/0000001a130b3f91
Other Wikipedia audio articles at:
https://www.youtube.com/results?search_query=wikipedia+tts
Upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts
Speaking Rate: 0.8854659769662632
Voice name: en-AU-Wavenet-A


"I cannot teach anybody anything, I can only make them think."
- Socrates


SUMMARY
=======
In computer science, garbage collection (GC) is a form of automatic memory management. The garbage collector, or just collector, attempts to reclaim garbage, or memory occupied by objects that are no longer in use by the program. Garbage collection was invented by John McCarthy around 1959 to simplify manual memory management in Lisp.Garbage collection is essentially the opposite of manual memory management, which requires the programmer to specify which objects to deallocate and return to the memory system. However, many systems use a combination of approaches, including other techniques such as stack allocation and region inference. Like other memory management techniques, garbage collection may take a significant proportion of total processing time in a program and, as a result, can have significant influence on performance. With good implementations and with enough memory, depending on application, garbage collection can be faster than manual memory management, while the opposite can also be true and has often been the case in the past with sub-optimal GC algorithms.
Resources other than memory, such as network sockets, database handles, user interaction windows, and file and device descriptors, are not typically handled by garbage collection. Methods used to manage such resources, particularly destructors, may suffice to manage memory as well, leaving no need for GC. Some GC systems allow such other resources to be associated with a region of memory that, when collected, causes the resource to be reclaimed; this is called finalization. Finalization may introduce complications limiting its usability, such as intolerable latency between disuse and reclaim of especially limited resources, or a lack of control over which thread performs the work of reclaiming.