Yeah, I got that too. It appears it’s also connected to esx_status.
More info, but no solution so far: