ProppFrexx ONAIR quits with .NET Runtime error

You found a bug or have any issues? Please post them here!
phonic
Posts: 221
Joined: 06 Mar 2019 14:45

ProppFrexx ONAIR quits with .NET Runtime error

Post by phonic » 03 Jan 2020 19:08

Below are the two entries (Application error and .NET Runtime) it does not appear to have been caught in the error.log but only in the windows application logs with the second being more useful for debugging:

Application Error:
Faulting application name: ProppFrexx ONAIR.exe, version: 4.1.5.3, time stamp: 0x5dff6857
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526
Exception code: 0xc0000005
Fault offset: 0x00000000000072a6
Faulting process ID: 0x35bc
Faulting application start time: 0x01d5bd0bd4048ac0
Faulting application path: C:\Program Files\radio42\ProppFrexx ONAIR\ProppFrexx ONAIR.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 787dde19-e1b6-4b58-a588-241e43dbaec1
Faulting package full name:
Faulting package-relative application ID:

.NET Runtime:

Application: ProppFrexx ONAIR.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Un4seen.Bass.Bass.BASS_StreamFree(Int32)
at ProppFrexx.MediaEntry.ReadTagInfo(Boolean, Int32)
at ProppFrexx.MediaEntry.GetTagInfo(Boolean, Int32)
at ProppFrexx.Advertising.OverlayContent.doCs(ProppFrexx.MediaEntry)
at ProppFrexx.Advertising.OverlayContent.koCc(ProppFrexx.Advertising.OverlayProgram)
at ProppFrexx.Advertising.OverlayContent.ResolveContent(ProppFrexx.Advertising.OverlayProgram, System.Threading.WaitCallback, Boolean)
at ProppFrexx.ProppFrexx_ONAIR.x6Pc(System.Collections.Generic.List`1<ProppFrexx.Advertising.OverlayProgram>)
at ProppFrexx.ProppFrexx_ONAIR+eMj.XoTB()
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Last edited by phonic on 12 Jan 2020 17:40, edited 1 time in total.

User avatar
radio42
Site Admin
Posts: 6064
Joined: 05 Apr 2012 16:26

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by radio42 » 04 Jan 2020 10:38

I’ll take a look at it.
It looks like an error in the audio lib I am using. So I need to report it to the lib developer. This might take a bit.

Can you reproduce the error? Ie. is it happening regularly?
Or is it happening always with the same audio track?

phonic
Posts: 221
Joined: 06 Mar 2019 14:45

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by phonic » 04 Jan 2020 13:30

radio42 wrote:
04 Jan 2020 10:38
I’ll take a look at it.
It looks like an error in the audio lib I am using. So I need to report it to the lib developer. This might take a bit.

Can you reproduce the error? Ie. is it happening regularly?
Or is it happening always with the same audio track?
The error is a new one for me, and only happened the once to my knowledge.

Apart from upgrading to 4.1.5.3 after Christmas, nothing has changed. The timing of the error at 08:27.05 relates to the Traffic update overlay that would have just shown and started its 3 minute count down to 08:30.
The playlist at that time was an automated script that has been used may times before and this morning too without issue.
The traffic overlay is a live traffic update downloaded via a script and plays with a sound bed(using standby players) followed by weather, and has not changed for many months.

User avatar
radio42
Site Admin
Posts: 6064
Joined: 05 Apr 2012 16:26

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by radio42 » 04 Jan 2020 15:22

The error happens during TAG reading of the traffic audio file. So could it be, that the file was ‚just‘ changed (newly downloaded), while the old file was just accessed?

phonic
Posts: 221
Joined: 06 Mar 2019 14:45

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by phonic » 04 Jan 2020 18:20

radio42 wrote:
04 Jan 2020 15:22
The error happens during TAG reading of the traffic audio file. So could it be, that the file was ‚just‘ changed (newly downloaded), while the old file was just accessed?
The traffic and weather are updated along with the news at XX:56 each hour time for the hourly news to a folder called news that ProppFrexx script uses to play-out, so it should not be an issue as traffic and weather goes out at XX:30 with the overlay displaying at XX:37.

I'm not sure why it would error on reading the TAG, as the file should not have changed since XX:56. I'll double check the logs and see if anything strange happened on that occasion.

User avatar
radio42
Site Admin
Posts: 6064
Joined: 05 Apr 2012 16:26

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by radio42 » 06 Jan 2020 14:58

If that ever happens again and for more info, can you get a dump file for the crash? You can use the ProcDump tool to generate it:

https://technet.microsoft.com/en-us/sys ... 96900.aspx

For example, run "procdump -e -ma -x . ProppFrexx ONAIR.exe". Then ZIP and send me the generated dump file to have a look at here.

phonic
Posts: 221
Joined: 06 Mar 2019 14:45

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by phonic » 06 Jan 2020 21:08

Just had another .NET Runtime error that ended Proppfrexx ONAIR in the middle of the live show at 16:38 this evening:

Application: ProppFrexx ONAIR.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Un4seen.Bass.Bass.BASS_StreamFree(Int32)
at ProppFrexx.MediaEntry.ReadTagInfo(Boolean, Int32)
at ProppFrexx.MediaEntry.GetTagInfo(Boolean, Int32)
at ProppFrexx.ScriptLibrary.CheckGlobalSongHistory(ProppFrexx.MediaEntry, Boolean, Boolean)
at ProppFrexx.ScriptLibrary.B6Vc(ProppFrexx.MediaEntry, Boolean, Boolean)
at ProppFrexx.ScriptLibrary.GetNextTracks(System.Object, System.DateTime, System.DateTime, Int32)
at ProppFrexx.Playlist.YgDC(System.DateTime, System.DateTime, Byte, ProppFrexx.MediaEntry, Boolean)
at ProppFrexx.Playlist.ggD6(Boolean, Byte)
at ProppFrexx.Playlist.VgDg(Byte)
at ProppFrexx.Playlist+LJy.moxA()
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
at System.Threading.ThreadPoolWorkQueue.Dispatch()

User avatar
radio42
Site Admin
Posts: 6064
Joined: 05 Apr 2012 16:26

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by radio42 » 06 Jan 2020 21:12

"Perfect"... see my above comments to create a crash dump...

phonic
Posts: 221
Joined: 06 Mar 2019 14:45

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by phonic » 06 Jan 2020 23:15

Just restarted ProppFrexx with Procdump64.exe but getting many exception errors as shown in the screen shot.
Attachments
Screenshot 2020-01-06 at 22.12.35.png

User avatar
radio42
Site Admin
Posts: 6064
Joined: 05 Apr 2012 16:26

Re: ProppFrexx ONAIR quit with .NET Runtime error

Post by radio42 » 07 Jan 2020 21:05

Another way to get a dump file (instead of using ProcDump) is by applying this "localdumps-full" registry entry:

www.un4seen.com/stuff/localdumps.zip

Windows will then generate a dump file in the %LOCALAPPDATA%\CrashDumps folder whenever a crash occurs. After you have got a dump file for the crash, you can use the "localdumps-off" registry file to disable the dump file generation.

Please try this and send a crash dump file to me. THX

Could it be, that the crash is caused by a particular audio file (which is maybe corrupt)?
As in the 2nd crash it is again caused during the TAG reading.

Nor me or any other customer has ever reported such an error, as such, I believe it must be somehow very specific.

Post Reply

Who is online

Users browsing this forum: No registered users and 10 guests