Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
If it's audio, and it's all coming from the same source, then...the source is the problem.
Check your free memory, running proc usage, and general util of your instance. Sounds like you're taxing it too much.
Would also be helpful to know "how" you are hearing this audio. Directly connected speaker, Bluetooth, WiFi...etc.
Let's discuss the chromebook since that's where i want the issue addresses first. It's a chromebook with the fully kiosk app running and it displays my home assistant internal address in the web browser. Through the kiosk app it's a destination for media playback and the sound comes out of the chromebook speakers. The vm is assigned 24gb of ram and it's using 8 of that and it's using less than 1% of the 32 cpus i've assigned to it. If you're wondering, the hardware is an old dual cpu server with more resources than i could ever hope to use so i over fed most of the vms i'm running. I doubt it's a hardware issue on the server side but i'm willing to try anything.
What method did you use to install on this Chromebook?
Also, it's a Chromebook, so it doesn't have 32 CPUs. Maybe you mean cores, which would even be weird for a Chromebook.
The home assistant vm has 32 cores, the chromebook i'm not sure. I installed the fully kiosk app using the google play store.
Report back with the model of your Chromebook and we might be able to say what's happening. Otherwise, restart it, and see if the problem disappears.
The issue is either the chromebook or the fully kiosk app, and i'm thinking it's the app. Post reboot it won't let me play music from or to the chromebook now.