ProppFrexx ONAIR User-Forum

Hi,

We've juste make an upgrade of our streaming server infrastructure and on each time the Icecast2 service (or system network availability) was closed on our server (server reboot for instance), PF crashed.

There seems to be a problem somewhere
Terminating just one source on the server side had no effect on PF, but ending all the connexion at the same time seems to create some issue.
Here we have 8 Icecast clients running on PF (routed over two different network interfaces).

Thanks for your help !


Here is the log :
Nom de l’application défaillante ProppFrexx ONAIR.exe, version : 4.2.7.4, horodatage : 0x61d5f711
Nom du module défaillant : ntdll.dll, version : 10.0.19041.1466, horodatage : 0xe2f8ca76
Code d’exception : 0xc0000374
Décalage d’erreur : 0x00000000000ff199
ID du processus défaillant : 0x22d4
Heure de début de l’application défaillante : 0x01d81912cb5722d5
Chemin d’accès de l’application défaillante : C:\Program Files\radio42\ProppFrexx ONAIR\ProppFrexx ONAIR.exe
Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\ntdll.dll
ID de rapport : 8382d8e4-052c-41a3-b618-25b58711a61e
Nom complet du package défaillant :
ID de l’application relative au package défaillant :

What you posted looks like a generic windows error reported by the windows event log. Typically this indicates a heap (memory corruption error).
This could have various root reasons, as drivers (e.g. network) which are being used by ProppFrexx might cause this...up to real memory defects.
But if the error is really related to updating your streaming server infrastructure that wouldn't indicate a hardware issue.
I assume, that the streaming server infrastructure (ICEcast2) is running on a different hardware?!
So most probably it is a timing issue with releasing network connections all at the same time.

Have you checked, if you can also find any related entry in the ProppFrexx file called "Error.log" (located in the ProppFrexx AppDataUser folder; e.g. %appdata%\radio42\ProppFrexx ONAIR\4.0\)?
If yes, (which I do not assume), this would however indicate, that the error indeed is on the ProppFrexx side.
If not, the error in somewhere else in the system, most probably the network driver of one of the interface cards.

You're most probably right then (no error log from PF).
Thank you for your time.

Best regards

Have you tried to disconnect them all manually, that would give some delay between the stops, just to see, if it is related to a specific network card or a timing issue.
Or you even call Stop All Servers from ProppFrexx, does that also make it crash?