eugenet8k
commented
2 years ago actually, it crashes every day, so it's fairly unreliable with my amount of speakers and the latest macOS version.
Closed eugenet8k closed 2 years ago
eugenet8k
commented
2 years ago actually, it crashes every day, so it's fairly unreliable with my amount of speakers and the latest macOS version.
philippe44
commented
2 years ago Can you try to have it running on anything else to see if this is a macOS build or not? Like a Pi or any Linux machine?
eugenet8k
commented
2 years ago @philippe44 yeah, I got the same idea another day. I will try it on the RespberryPi with my zoo of chromecast devices and see how it runs.
eugenet8k
commented
2 years ago @philippe44 it seems it's working on pi totally reliable, I was running for a few days and didn't have a single crash. Although I wasn't able to generate a config file on pi, got this error:
pi@raspberrypi:/var/lib/airconnect $ ./aircast-arm -i config.xml
[20:11:20.847125] main:974 Starting aircast version: v0.2.50.5 (May 24 2021 @ 15:12:13)
[20:11:20.847601] main:982 no config file, using defaults
[20:11:20.847849] Start:732 Binding to 10.0.1.15
[20:11:20.879641] AddCastDevice:669 [0x12c9a10]: adding renderer (Basement Wifi)
[20:11:20.880504] AddCastDevice:675 [0x12c9a10]: creating MAC 12c9a1a
Segmentation faultBut, since I already had a macOS setup, I was able to generate config.xml there and use it at pi. LOL. After all, it seems all good now, thanks for the terrific software!
philippe44
commented
2 years ago The fault might be an access right issue where you are trying to create the config.xml.
Re MacOS, I really don't know then. I'm using cross-compilation and that setup is old but it took me quite a while to be able to generate for MacOS from Linux and I'm not very motivated to update it. The symbols are still here in this version, so try to run it from command line using gdb or any debugger and see where it crashes.
It seems to be in the mDNS responder but then it should crash everywhere (I mean on the Pi as well) if you have a machine that is sending a request that causes the issue.
Now, there is also CVE-2017-12087 which might be an issue but that would mean there is an attacker on your network. Unlikely, but maybe you want to check. Still, I'll apply the fix but as it used in many of my application, it will take me a bit of time
philippe44
commented
2 years ago Closed for inactivity
Thank you for the great software! I have a big number of chromecast devices (10+) and I run aircast-osx-multi as service on macOS v11.5.2. Usually, it works for a day or so and then crashes. This is the log from OS Crash Reports: