I just had an issue of a segfault which occurred while an automation was running for my chromecast audio. This happened once before while I was on 0.55. I am currently on 0.57.2 (just upgraded today). I was curious to see if there was a known issue when I came across this. I do not have any problems with 0.57.2 recognizing my chromecast audio however after digging deeper I noticed I am also on version 1.28.100555 and did not recall ever signing up for this preview but upon checking within the Home app I found that it was set to receive the preview software. I have now unchecked it but it makes me wonder if this is the reason for my sudden segfaults when sending tts or an audio file to the chromecast audio.
Nov 08 16:30:00 raspberrypi hass[12389]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: service_call_id=1971404368-128, domain=media_player, service=volume_set, service_data=volume_level=0.3, entity_id=media_player.chromecastaudio1>
Nov 08 16:30:00 raspberrypi hass[12389]: INFO:pychromecast.controllers:Receiver:Launching app CC1AD845
Nov 08 16:30:00 raspberrypi hass[12389]: INFO:pychromecast.controllers:Receiver:setting volume to 0.3
Nov 08 16:30:00 raspberrypi systemd[1]: home-assistant.service: Main process exited, code=killed, status=11/SEGV
Nov 08 16:30:00 raspberrypi systemd[1]: home-assistant.service: Unit entered failed state.
Nov 08 16:30:00 raspberrypi systemd[1]: home-assistant.service: Failed with result ‘signal’.