Strange to declare this one field volatile, and the others not.
We should double-check what synchronization guarantees there are for the lifecycle methods, for whether one needs to declare volatile or if something will have gone through a synchronized block (or some such) in the framework already.