ProppFrexx ONAIR User-Forum

Posted: **22 May 2014 20:25**

Again pf crashed.
From event viewer:

Faulting application name: ProppFrexx ONAIR.exe, version: 3.0.13.24, time stamp: 0x537dbff8
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0a5903fd
Faulting process id: 0x1388
Faulting application start time: 0x01cf75e994cbd24e
Faulting application path: C:\Program Files (x86)\radio42\ProppFrexx ONAIR\3.0\ProppFrexx ONAIR.exe
Faulting module path: unknown
Report Id: 4f5b8d99-e1dd-11e3-9f02-0025227ade5e

and

Code: Select all

Application: ProppFrexx ONAIR.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at Un4seen.Bass.AddOn.Enc.BassEnc.BASS_Encode_StopEx(Int32, Boolean)
   at Un4seen.Bass.Misc.BaseEncoder.Stop()
   at Un4seen.Bass.Misc.BaseEncoder.a(Boolean)
   at Un4seen.Bass.Misc.BaseEncoder.Finalize()

I created a dump file. I am sending you the link in pm.

Posted: **22 May 2014 20:25**

Thanks for sending me the dump file.
Unfortunately it is a 64-bit DUMP file, but ProppFrexx is a 32-bit application.
You probably used the standard 64-bit TaskManager to do that?!

So, you need to use 32bit TaskManager, if you would like to collect a dump of a 32bit process (sorry that I did not mention that precisely earlier).
So, if your process is 32bit (note, that all processes haing a '*' at the end in the TaskManager are 32bit processes), then you need to run 32bit version of the TaskManager on a 64bit OS.
The 32bit TaskManager is located in the "C:\Windows\SysWOW64" folder and the name of the file is "taskmgr.exe".

See here for details: http://blogs.msdn.com/b/amb/archive/201 ... 63879.aspx

Posted: **25 Jun 2014 15:09**

Did it ever crash again?

Posted: **25 Jun 2014 17:30**

Bernd that crash occurred while I was testing PF.
On those tests my icecast server was up and down and PF was trying to connect, so Connected, disconnected ... etc was the case. At one of those connection attempts this crash happened.
Now that I am using PF in a stable icecast connection OnAir, have no problems.
Except when I try to close PF that hangs at "Closing TCP connections" and I have to force close it.
But this is happening only when I need to update PF, otherwise I have no reason to close it.

Posted: **28 Jun 2014 07:43**

Some more info about Closing TCP Connections hung:
Before my last update I first closed the streaming servers. Their status changed from CONNECTED to STOPPED.
Then I tried to update PF and while Updater was trying to close PF it again hung at "Closing TCP Connections".
I noticed that the status of the encoders changed from STOPPED to CLOSING.
Does it need to Close if it is already Stopped ?
Maybe this might help you find the bug.

Posted: **28 Jun 2014 21:27**

Yes, that is normal.
I am still absolutely not able to reproduce the issue and as far as I can tell no other user is having such issue at the moment.
And as already said, closing the TCP Connection is simply closing a network socket, which is a single OS call. And if that hangs, there must be something wrong in the network.

ProppFrexx ONAIR User-Forum

Application crash :(

Application crash :(

Re: Application crash :(

Re: Application crash :(

Re: Application crash :(

Re: Application crash :(

Re: Application crash :(