Double-checked locking is broken without volatile

Without volatile, the constructor's writes can be reordered after the field assignment. A second thread then sees a non-null reference to a half-built object - and the bug appears only on a weak memory model, under load, in production.

Full code & output

This topic is available to PRO members.

Sign in Create a free account

Run this yourself in the Online Java Compiler, spin up a live REST API in the API Sandbox, or practise with Java interview questions.

Published 2026-08-25