I am running a LiquidSoap server with a relatively simple JavaScript backend
(Express). The LiquidSoap goes and requests an audio track from the backend at
a specified URL, but sometimes the backend has no tracks to give out - in this
case, the backend returns a 500. When this occurs, the LiquidSoap server is
expected to fall back, which it does. The system works perfectly when there are
tracks, but when there are no tracks for a long time, trouble begins to brew.
At around the time that the fallback ends and it crossfades into itself (say,
after 3-4 minutes), LiquidSoap produces a segmentation fault trying to
constantly request the backend for a track.
The cause of the segmentation fault is unknown and remains under investigation.
Because I am running LiquidSoap inside a Docker container, it is a little
difficult to get a core dump.
Here is a shortened version of my script:
```python
set("log.file.path", "/tmp/liquidsoap.log")
set("log.stdout", true)
set("log.level", 4)
url = "http://localhost/next-song";
url2 = "http://example.com/fallback.mp3";
main_source = smart_crossfade(
fallback(track_sensitive=false, [
single(url),
mksafe(audio_to_stereo(single(url2)))
])
)
output.icecast(%fdkaac, host="172.0.1.3", port=8000, mount="/stream.aac",
main_source)
```
Assistance in investigating the issue is appreciated. Thanks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/586------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
