You can kill pulseaudio process freely :) It's restarted via socket activation. To make sure: you never had this problem before the update? I remember one recent fix about the AMD chip (dropping the workaround), and that could be the cause. OTOH, the drop was done because it leaded to this kind of problem. So, it seems very sensitive and depending on the chip, revision, whatever...