packratting : Java Glossary
home P words local find no local find frame, full screen Google search web for topic jump to footer translate with Babelfish by Roedy Green ©1996-2008 Canadian Mind Products
Go to : punctuation 0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (all)
packratting
Sometimes called loitering or object leaks. Holding references to Objects long after the practical life of the Object has passed. This is a form of memory leak, though calling it a true memory leak would be like blaming the garbage man because your Mom wrote "DO NOT DISCARD" on all the bundles of junk in her attic. In Java, true memory leaks are theoretically impossible (unless you use JNI or your JVM is buggy), though packratting is common. In fact it is almost impossible to write a program that nullifies references to every object the instant it will never be needed again. So every program is guilty of minor packratting.

Java talks to the underlying GUI which is typically written in C++ which does not have automatic garbage collection. Therefore you see kludges in Java dispose methods, to help it along. If you fail to use dispose properly, Java won’t run out of RAM, but the GUI will. Failing to use dispose create true memory leaks. Here are some common packratting situations:


CMP_homejump to top
CMP logo
feedback Please email your feedback for publication, errors, omissions, broken/redirected link reports
and suggestions to improve this page to Roedy Green : feedback email
made with CSS
HTML Checked!
ICRA ratings logo
mindprod.com IP:[65.110.21.43]
Your face IP:[38.103.63.16] The information on this page is for non-military use only.
You are visitor number 12,969. Military use includes use by defence contractors.
You can get a fresh copy of this page from: or possibly from your local J: drive (Java virtual drive/Mindprod website mirror)
http://mindprod.com/jgloss/packratting.html J:\mindprod\jgloss\packratting.html