As per comments on https://chromium-review.googlesource.com/c/541685, the shared memory logic can likely be encapsulated in the SensorReadingSharedBufferReader and eliminate some bookkeeping in the SensorProxy object (e.g. the shared_buffer_ member). This can happen by means of an Initialize() method returning a boolean, an approach that would be similar to the current shared_memory_seqlock_reader implementation..