You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Using remote urls in a playlist seems to cause a short high memory usage when a file is being (down-) loaded. A file of size 300 MB causes Liquidsoap to consume around 1 GiB of memory for a short period. Only after some time it drops down to around 100 MiB and slowly rising up to approximately the size of the file (which is expected). For a file of size 60 MB it rises up to around 500 MiB of memory usage.
When the files are read from a local disk instead, the high peak does not occur.
Describe the bug
Using remote urls in a playlist seems to cause a short high memory usage when a file is being (down-) loaded. A file of size 300 MB causes Liquidsoap to consume around 1 GiB of memory for a short period. Only after some time it drops down to around 100 MiB and slowly rising up to approximately the size of the file (which is expected). For a file of size 60 MB it rises up to around 500 MiB of memory usage.
When the files are read from a local disk instead, the high peak does not occur.
To Reproduce
This is the config being used:
Playlist:
Expected behavior
Expecting the same behavior that occurs when using local files.
Version details
Install method
Using docker-compose and docker image from https://hub.docker.com/r/savonet/liquidsoap.
The text was updated successfully, but these errors were encountered: