Java memory (Stack) allocation for local variables

• Each thread has a private stack.
• Each method has a private stack frame within that thread's stack.

Stacks are associated with thread in a one-to-one mapping. Stacks are absolutely not associated with methods and classes.

The way to reason about all this is that the local variables of a method are private to each invocation of that method.

Every thread has it's own stack.

• Whenever you use new, an object is created on the heap.
• Local variables are stored on the stack. That includes primitives (such as int) and the references to any objects created. The actual objects themselves aren't created on the stack, as I mentioned when you use new they'll be created on the heap.

I have question that weather a new STACK is being created for each method??

The same stack is being used when a method is called. A method will create it's own little section on the stack called a "stack frame" that's used to hold it's local variables.

It's just like a stack of plates, when a method is called a plate is added to the top of the stack (a stack frame), and when that method ends the plate is removed from the stack. All of that method's local variables will be destroyed with it, but the actual objects created with new won't.

The JVM's garbage collector will look after destroying objects on the heap (the one's created with new) when it sees you no longer need them.