Java Class / en - Storage

In addition to what your partner @MatiEzelQ tells you, the instances have a life cycle and this has to do with the garbage collection .

Currently there are two "types" of spaces for instances:

• Young generation
• Old generation

For each type of space there are different containers.

Young generation / New generation

This space contains 3 containers:

• Eden: here we store the objects that we just instantiated.
• Survivor 0: Here the objects that have no reference are stored at the moment of passing the garbage collector.
• Survivor 1: If the garbage collector still finds objects without reference in Survivor 0, they are passed to Survivor 1.

Old generation / Old generation

If when the collector goes through the Survivor 1 finds that the objects there still have no reference, they become part of the old generation.

This generation contains 2 containers:

• Ternured: here arrive the objects that do not follow without reference when the collector went through the Survivor 1. The collector will generally pass through here when the space is full , releasing the objects definitively .
• Permanent: here the JVM loads the classes it needs for its operation. The collector will not go through here because these instances are permanent.

Although I understand, the problem you say is that while you are installing more classes, you are going to be occupying more RAM memory with your program. If you are interested in an instance, you have two storage places (both in the ram):

The instances of your classes themselves are stored in the heap. That is, when doing a new ClaseA , the only thing you are doing is creating the instance in the heap. Now if you make ClaseA a = new ClaseA(); you are creating a variable in the STACK (called: a) that has a reference to the instance, which is stored in the HEAP.

I leave an image where you can see, perhaps, more clearly what I try to explain:

I hope I have understood your doubt well.