Author Topic: Stange Error Log Entries  (Read 75 times)

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9385
Using 3.6.8881 through 3.6.8891 on Win10

@Steven...
I haven't had any odd behavior in MB, nor has this error appeared in a popup. I was cleaning up ErrorLog.dat file and found about a dozen of these dating back to April 26, which is the last time I cleared out the error log. So it could have been appearing before that. Thought you might want to know about this in case it's something to be concerned with.

Code
5/8/2024 3:26:27 PM - 10.0.19045.0 - 3.6.8891.37045P - System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. ---> System.ObjectDisposedException: Safe handle has been closed
   at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne()
   at #=zuOZ1Asvf3$pJj74FO44nySADQMXts4HUjuUquzs=.#=qQXX75rJ4qCNRMNLWLvSe6Q==._Lambda$__1()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.ObjectDisposedException: Safe handle has been closed
   at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne()
   at #=zuOZ1Asvf3$pJj74FO44nySADQMXts4HUjuUquzs=.#=qQXX75rJ4qCNRMNLWLvSe6Q==._Lambda$__1()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()<---
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34402
its related to the replaygain analyser. Do you have it replaygain analysis enabled in Tags(2)/ in the tags section?
If you just run it manually, do you sometimes cancel the analysis mid-way through?

in any case the usual downloads link is updated with a change to address the issue
Last Edit: May 16, 2024, 12:15:56 PM by Steven

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9385
Thanks Steven.

No, I do not have analysis enabled anywhere that I checked. I do analyze all my music as part of my workflow when added new albums to my collection. I evoke it via a toolbar button and I do remember stopping it a few times in the past week or so, but I usually let it finish.

I will grad the patch and report back if I see it again. I'll test a couple of time with and without interrupting the analysis.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here