On Sat, January 14, 2012 11:46, mark@xxxxxxxxxxxxxxxxxxxx wrote: > I am confused, but then again that is hardly a breaking news. How does > memory leak? It's a software development term (my day job). Basically, it means the application loses track of a piece of memory -- so when the app is done with the memory, it doesn't get freed and made available for later uses. Depending on the system and the exact source of the trouble, it might get freed when that application is closed, but in extreme cases it may not be freed until the OS is restarted. The set of memory being managed dynamically is sometimes referred to as a "pool", so it kind of makes sense to describe this kind of error, where memory is lost out of the "pool", as a "leak". Nothing is physically moving around or anything really weird like that :-). -- David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info
