packratting : Java Glossary

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 (Java Native Interface) or your JVM (Java Virtual Machine) 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 (Graphic User Interface) 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 (Random Access Memory), but the GUI will. Failing to use dispose create true memory leaks. Here are some common packratting situations:


CMP homejump to top

available on the web at:

http://mindprod.com/jgloss/packratting.html
ClustrMaps is down

optional Replicator mirror
of mindprod.com
on local hard disk J:

J:\mindprod\jgloss\packratting.html
logo
Please the feedback from other visitors, or your own feedback about the site.
Blog
IP:[65.110.21.43]
Your face IP:[107.20.131.154]
You are visitor number 24,852.