Question: From the Java memory model, we know that every thread has its own thread stack, and that local variables are placed in each thread's own thread stack.

And that *other* threads can't access these local variables.

So in which case should we synchronize on local variables?

Answer: 
You are talking about the below case:

```
public class MyClass {
    public void myMethod() {
        //Assume Customer is a Class
        Customer customer = getMyCustomer();
        synchronized(customer) {
            //only one thread at a time can access customer object
              which ever holds the lock
        }
    }
}

```

In the above code, **`customer` is a local reference variable, but you are still using a synchronized block** to restrict access to the object `customer` is pointing to (**by a single thread at a time**).

In Java memory model, **objects live in heap (even though references are local to a Thread which live in a stack) and synchronization is all about restricting access to an object on the heap** by exactly one thread at a time. 

In short, **when you say local variable (non-primitive), only reference is local, but not the actual object itself i.e., it is actually referring to an object on the heap** which can be accessed by many other threads. Because of this, you need synchronization on the object so that single thread can only access that object at a time.
There are two situations:

1. The local variable is of a primitive type like `int` or `double`.
2. The local variable is of a reference type like `ArrayList`.

In the first situation, you *can't* synchronize, as you can only synchronize on Objects (which are pointed to by reference-type variables).

In the second situation, it all depends on what the local variable points to. If it points to an object that other threads (can) also point to, then you need to make sure that your code is properly synchronized.

Examples: you assigned the local variable from a `static` or instance field, or you got the object from a shared collection.

If, however, the object was created in your thread and only assigned to that local variable, and you never give out a reference to it from your thread to another thread, and the objects implementation itself also doesn't give out references, then you don't need to worry about synchronization.