Skip to main content

IMPORTANCE OF CLEAN UP: finalization & garbage collection



To clean up an object, the user of that object must call a cleanup method at the point the cleanup is desired. This is straightforward, but it collides a bit with the C++ concept of destructor. In C++ all object is created as a local (i.e., on the stack –not possible in java), then the destruction happens at the closing curly braces of the scope in which the object was created. Programmers know about the importance of initialization, but often forget the importance of clean up. After all who need to clean up int?  Java has the garbage collector to reclaim the memory of objects that are no longer used.  Here I am considering an unusual case: let java object allocate a special memory without using new.  Garbage collector only knows how to release memory allocated with new, so it would not know how to release the special memory. To handle that type of situation /cases, java provides a method called finalize () that define in the class.
How it is supposed to work & What the finalize() for ?
When garbage collector is ready to ready to release the storage used by object, it will first call finalize(), and only on the next garbage-collection pass will it reclaim the object’s memory.  So if we use finalize (), it gives the ability to perform cleanup at the time of garbage collection. The C++ programmers, might initially mistake finalize () for the destructor in C++, which is a function that is always called when object is destroyed. It is important to distinguished between C++ and Java here, because in C++, objects always get destroyed , where as in Java, object do not always get garbage collected.
ð Object might not get garbage collected.
ð Garbage collection is not destruction.
Java has no destructor or similar concept, so we must create an ordinary method to perform cleanup.
ð Garbage collection is only about memory.
The existence of garbage collector is to recover memory that program no longer using.  So any activity that is associated with garbage collection, most notably finalize () method, must also be only about memory and its de-allocation.
Anurag

Comments

Popular posts from this blog

Standard and Formatted Input / Output in C++

The C++ standard libraries provide an extensive set of input/output capabilities which we will see in subsequent chapters. This chapter will discuss very basic and most common I/O operations required for C++ programming. C++ I/O occurs in streams, which are sequences of bytes. If bytes flow from a device like a keyboard, a disk drive, or a network connection etc. to main memory, this is called   input operation   and if bytes flow from main memory to a device like a display screen, a printer, a disk drive, or a network connection, etc., this is called   output operation . Standard Input and Output in C++ is done through the use of  streams . Streams are generic places to send or receive data. In C++, I/O is done through classes and objects defined in the header file  <iostream> .  iostream  stands for standard input-output stream. This header file contains definitions to objects like  cin ,  cout , etc. /O Library Header Files There are...

Genotype Representation

Binary Representation This is one of the simplest and most widely used representation in GAs. In this type of representation the genotype consists of bit strings. For some problems when the solution space consists of Boolean decision variables – yes or no, the binary representation is natural. Take for example the 0/1 Knapsack Problem. If there are n items, we can represent a solution by a binary string of n elements, where the x th  element tells whether the item x is picked (1) or not (0). For other problems, specifically those dealing with numbers, we can represent the numbers with their binary representation. The problem with this kind of encoding is that different bits have different significance and therefore mutation and crossover operators can have undesired consequences. This can be resolved to some extent by using  Gray Coding,  as a change in one bit does not have a massive effect on the solution. Real Valued Representation For problems where we want to define ...

Data Warehousing - An Overview

Anurag Information Technology (IT) has historically influenced organizational performance and competitive standing. The increasing processing power and sophistication of analytical tools and techniques have put the strong foundation for the product called data warehouse. There are a number of reasons that any organization should consider a data warehouse, which can be the critical tool for maximizing the organization’s investment in the information it has collected and stored throughout the enterprise. IT managers need to understand the rationale and benefits of data warehouses because they may need to design and implement, or procure this kingpin of business intelligence. The data warehouses are supposed to provide storage, functionality and responsiveness to queries beyond the capabilities of today's transaction-oriented databases. Also data warehouses are set to improve the data access performance of databases. Traditional databases balance the requirement of data access w...