One day streaming

Started by hub73, 6 Dec '22 - 13:57

hub73

Hello.
My broadcast program works well with Bass. I use Icecast to stream. After about 10 hours of stability streaming. (CPU used by Bass and correct memory) I have no video display at all and even on a Window server 2012 with 32 GB of RAM and dedicated I get a black screen and I can't recover anything. No sound and forced reboot.

How do you know what bass is doing at the moment? a log file somewhere to understand and what resources it uses (mixer). I have no error message from BASS. Thank you for your advice, then it is not necessarily BASS the problem by another thing inside the program.
It's a bit hard to debug because I don't know how bass handles itself. It would be cool to be able to display info on its current state. (Note that BASS also records sound during the stream to a file)

Thanks for your ideas.

Ian @ un4seen

The entire system freezes? That seems unlikely to be software-related, at least not user software (perhaps a driver). Please see if you can reproduce it on another system.

hub73

It does this from all computers. The audio files are stored on the same Synology NAS. The only thing I found was to stop the entire program and restart it half a day to reach 24 hours. When we stream for a while. A file whose size would increase? A memory area that would increase? Is there a way to know if all is correctly freed from BASS ? Sometimes the display resolution is changed, the software keeps running and eventually freezes.

Ian @ un4seen

The display going black and/or changing resolution sounds like some weirdness is going on there!

If you would like to check for resource leaks, you can use the BASS_CONFIG_HANDLES value (from BASS_GetConfig) to check for leaked BASS handles, eg. unfreed streams. You could also try monitoring your app's resource usage with Process Explorer:

   https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

hub73

Thank you very much Ian I will try all of this

hub73

QuoteIf you would like to check for resource leaks, you can use the BASS_CONFIG_HANDLES value (from BASS_GetConfig) to check for leaked BASS handles, eg. unfreed streams.
This is an essential command for debugging ! This seems to be an unfreed stream !