Answer
In a confirmed case, this was resolved by recreating the affected user's client profile from scratch. It's not an elegant fix and doesn't explain what corrupted the profile in the first place, but recreating the profile has reliably cleared this specific error when it appears without any other explanation.