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

Post a Comment

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...
Post a Comment
Read more

locking

DBMS Locking Part I (DBMS only) TECHNICAL ARTICLES -> PERFORMANCE ARTICLES [  Back  ] [  Next  ] DBMS is often criticized for excessive locking – resulting in poor database performance when sharing data among multiple concurrent processes. Is this criticism justified, or is DBMS being unfairly blamed for application design and implementation shortfalls? To evaluate this question, we need to understand more about DBMS locking protocols. In this article, we examine how, why, what and when DBMS locks and unlocks database resources. Future articles will address how to minimize the impact of database locking. THE NEED FOR LOCKING In an ideal concurrent environment, many processes can simultaneously access data in a DBMS database, each having the appearance that they have exclusive access to the database. In practice, this environment is closely approximated by careful use of locking protocols. Locking is necessary in a concurrent environment to as...
Post a Comment
Read more

Difference between net platform and dot net framework...

Difference between net platform and dot net framework... .net platform supports programming languages that are .net compatible. It is the platform using which we can build and develop the applications. .net framework is the engine inside the .net platform which actually compiles and produces the executable code. .net framework contains CLR(Common Language Runtime) and FCL(Framework Class Library) using which it produces the platform independent codes. What is the .NET Framework? The Microsoft .NET Framework is a platform for building, deploying, and running Web Services and applications. It provides a highly productive, standards-based, multi-language environment for integrating existing investments with next-generation applications and services as well as the agility to solve the challenges of deployment and operation of Internet-scale applications. The .NET Framework consists of three main parts: the common language runtime, a hierarchical set of unified class librari...
3 comments
Read more