I'm doing a bit of a deep dive into Java programming. As I'm reading a book I realize that similar to methods and associated local variables (stack variables), constructors also get to stack series the same way as methods (on each call, the rack goes on top of the call stack, and then gets "popped off" on completion (end of code block "}"). Repeat the process until the rack at the bottom of the stack finishes executing all the statements.
So, what I would like to understand is how come constructors also go to the stack instead of the heap memory (gc heap), aren't they supposed to be members of the object being instantiated (live on heap too)?
I tried understanding, but couldn't.