Stack and Heap memory object allocation

[sandybo]

Can any one let me know did this object allocation is right in stack and heap please check Image attached

[scarecrowkid]

Looks right to me.

Primitives data types also go on the stack.

[SurfMan]

If I'm not mistaken, guys, correct me if I'm wrong: the literal String "Hello" in the constructor for s3 (and "Hai" in s4) is also stored in the String pool, but it adds an extra String object on the heap that points to this pooled String.

That's why s1 == s2 will be true (same object reference) and s1 == s3 is false (different object references). Using s1.equals(s3) will be true, because that compares content and not reference.

[jim829]

I believe you are correct. Here is some test code. It presumes the default hash code is the memory address of the object.

public class StringMemory {
   public static void main(String[] args) {
      String a = new String("hello");
      System.out.println(Integer.toHexString(System.identityHashCode(a)));
      System.out.println(Integer.toHexString(System.identityHashCode(a.intern())));
   }
}

The code prints out two different values implying two different memory locations.

Regards,
Jim