illustrating volatile : is this code thread-safe?

Question

I\'m trying to illustrate the use and importance of volatile with an example that would really not give a good result if volatile was omitted.

Answer 1

UPDATE My answer is wrong, see answer from irreputable.

---

It's not thread-safe, since access to count is not there's only one writer thread. Should there be another writer thread, value of count would be become inconsistent to the number of updates.

Visibility of count value to main thread is ensured by checking stopped volatile inside getCount method. This is what is called piggybacking on synchronization in Concurrency in practice book.