faeran Posted Saturday at 07:54 PM Posted Saturday at 07:54 PM 1 hour ago, Madhead said: I submitted a bug report, but found no where to include the error log in event viewer so I'll just put it here. Application: LaunchBox.exe CoreCLR Version: 9.0.525.21509 .NET Version: 9.0.5 Description: The process was terminated due to an unhandled exception. Stack: at Unosquare.FFME.Container.MediaComponent.DecodeNextAVFrame() at Unosquare.FFME.Container.MediaComponent.ReceiveNextFrame() at System.Threading.Tasks.Parallel+<>c__DisplayClass32_0`2[[Unosquare.FFME.Common.MediaType, ffme.win, Version=7.0.361.1, Culture=neutral, PublicKeyToken=null],[System.__Canon, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].<ForEachWorker>b__0(Int32) at System.Threading.Tasks.Parallel+<>c__DisplayClass19_0`2[[System.__Canon, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Int32, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].<ForWorker>b__1(System.Threading.Tasks.RangeWorker ByRef, Int64, Boolean ByRef) at System.Threading.Tasks.TaskReplicator+Replica.Execute() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread) at System.Threading.Tasks.ThreadPoolTaskScheduler.TryExecuteTaskInline(System.Threading.Tasks.Task, Boolean) at System.Threading.Tasks.Task.InternalRunSynchronously(System.Threading.Tasks.TaskScheduler, Boolean) at System.Threading.Tasks.TaskReplicator.Run[[System.Threading.Tasks.RangeWorker, System.Threading.Tasks.Parallel, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a]](ReplicatableUserAction`1<System.Threading.Tasks.RangeWorker>, System.Threading.Tasks.ParallelOptions, Boolean) at System.Threading.Tasks.Parallel.ForWorker[[System.__Canon, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Int32, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](Int32, Int32, System.Threading.Tasks.ParallelOptions, System.Action`1<Int32>, System.Action`2<Int32,System.Threading.Tasks.ParallelLoopState>, System.Func`4<Int32,System.Threading.Tasks.ParallelLoopState,System.__Canon,System.__Canon>, System.Func`1<System.__Canon>, System.Action`1<System.__Canon>) at Unosquare.FFME.Engine.FrameDecodingWorker.ExecuteCycleLogic(System.Threading.CancellationToken) at Unosquare.FFME.Primitives.WorkerBase.ExecuteCyle() at Unosquare.FFME.Primitives.StepTimer+<>c__DisplayClass22_0.<ExecuteCallbacks>b__1() at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(System.Threading.Thread, System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread) at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart() And another log "Application Error": Faulting application name: LaunchBox.exe, version: 13.23.0.0, time stamp: 0x67fe0000 Faulting module name: coreclr.dll, version: 9.0.525.21509, time stamp: 0x67fe9d00 Exception code: 0xc0000005 Fault offset: 0x00000000002e5904 Faulting process ID: 0x2cc Faulting application start time: 0x01dc144b082af26d Faulting application path: G:\Emulators\LaunchBox\Core\LaunchBox.exe Faulting module path: G:\Emulators\LaunchBox\Core\coreclr.dll Report ID: 3a144205-89c5-40ab-81ba-0b64c306687e Faulting package full name: Faulting package-relative application ID: Both logs were made 2 seconds after eachother. That indicates you are still on version 13.23. Can you update to the beta, which is 13.24 beta 1, and see if you are still experiencing the issue? Quote
Gaming.Zone Posted Saturday at 09:17 PM Posted Saturday at 09:17 PM I can confirm the False Positive does not occur in the 13.24 beta 1 on my machine. I did not update Windows Defender definitions yet, so my PC was still at the same state as when I installed 13.23. Just an FYI. Thanks. 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.