2

I come from operating systems and background of C where the world is simple when code is compiled. Need to deal and understand stack, heap text section etc.

When I started learning Java(I do know about JVM and garbage collector), I got amused by static methods. As per my understanding all the instances of a class do get created in the heap and then do get cleaned. However, for a static method, you don't need an instance of the class.

So, can some one please explain how non static methods and static methods differ in memory model. Do both of them reside in the text section of the memory. Or I am messing up things completely.

Thanks

agent.smith
  • 9,134
  • 9
  • 37
  • 49
  • This is a duplicated query. See below: [static method vs non-static method][1] [1]: http://stackoverflow.com/questions/3903537/i-want-to-know-the-difference-between-static-method-and-non-static-method – David Lo Jan 23 '15 at 00:01
  • 1
    Methods, static or not, are part of class definition, and reside in the special memory section, separate from heap, same as in "C". – Dima Jan 23 '15 at 00:01
  • Odd, since both Java and C has stack, heap, static storage. The only difference is classes and instances, which can be dummied in C (and, in fact,Objective-C does this). – Hot Licks Jan 23 '15 at 00:03

2 Answers2

2

In Java, the bytecode for the classes (and that includes their methods, both static and instance) is part of the heap (usually in a special "permanent generation" section for long-lived objects).

Classes can be garbage-collected, too, but this usually does not happen much (only when the class was loaded from a non-system classloader and that whole classloader becomes obsolete, for example when a web application is unloaded).

However, for a static method, you don't need an instance of the class.

Right. But all methods are part of the class definition and loaded together when the class is loaded. Even if you never make an instance of a class, the code for all instance methods will be loaded into heap memory.

And then there is JIT compilation to native code: With Hotspot, the bytecode for frequently used methods is compiled further into native machine code. The result of that does go somewhere outside of the heap into native memory, and that only happens for methods that are actually being used (static or not).

Thilo
  • 257,207
  • 101
  • 511
  • 656
0

Your understanding that all instances of a class get created in the heap...

Not exactly correct, all classes get compiled into object byte code, otherwise the JVM has nothing to execute. Instance and static methods all generate the same object byte code. Even non-static classes only generate a single version of their object byte code. All instance classes have their own pointer to where their execution is in that single copy of byte code. The real difference is in the data members of the class. Each instance of a non-static class has to have its own copy of all the non-static data members (variables), but static data members only have a single copy in memory since static data members of a class are shared by all instances of that class static or non-static.

A static class or the static data members of a non-static class all have a single copy of themselves in memory.

A non-static class still has just a single copy of its object code in memory, it is only the non-static data that gets a copy in memory for each instance.

DAC
  • 707
  • 1
  • 6
  • 20