Jump to content

Been getting "Unhandled Exception" error since a few versions ago


diaz1510

Recommended Posts

diaz1510

I can't recall exactly which version it started from (and it may not even be caused by Emby), but it was at least 1 build before stable 3.0.7300, but I've been getting this error what seems to be randomly:

 

580413a09f96f_01.jpg

 

I thought it may fix itself when I went to 3.0.8000 but it didn't.  I went to the Beta version 3.1.188 the other day for an unrelated issue (the whole  rogue nfo  file and jumbled library/content type issue) and have stayed on it since then.  Other than the Unhandled Exception it seems to be running fine right now.

 

The error crashes Emby but I can just restart it each time and use it normally.  However, I will get this error intermittently.  Sometimes twice a week, sometimes twice a day.

 

I attached the logs, hopefully it helps.  Thanks!

 

Not sure if it's something on my system or if it's directly Emby.

server-63612230500.txt

unhandled_47babe93-b0c9-448c-ab93-d03e6f1b5f5f.txt

Link to comment
Share on other sites

Commodus

I've been getting the same error messages since Version 3.0.8100.0

I get two dozens of thee message box when I get home in the evening.

 

Logs580521819563d_Embylogs.png

 

Here is the content of one of those errors:

(my disk have a lot of free space and 16Gb ram is not even half full)

 

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
System.Net.Sockets.SocketException
   at System.Net.Sockets.Socket.EndSend(IAsyncResult asyncResult)
   at Rssdp.UdpSocket.<>c__DisplayClass4_0.<SendTo>b__0(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Rssdp.Infrastructure.SsdpCommunicationsServer.<SendMessageIfSocketNotDisposed>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Rssdp.Infrastructure.SsdpCommunicationsServer.<Repeat>d__29.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Rssdp.Infrastructure.SsdpCommunicationsServer.<SendMessage>d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Rssdp.Infrastructure.SsdpDevicePublisherBase.<SendSearchResponse>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_1(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
 

Link to comment
Share on other sites

diaz1510

Thanks for the report. Hopefully beta 193 resolves it.

Any idea what might be causing it?  Is it something on my system or is it an emby issue?

Link to comment
Share on other sites

Happy2Play

Well that unhandled is different then the first one.

An address incompatible with the requested protocol was used

Your system seems to be going crazy for all these "test.file" that are throughout your libraries also.

Link to comment
Share on other sites

diaz1510

Well that unhandled is different then the first one.

An address incompatible with the requested protocol was used

Your system seems to be going crazy for all these "test.file" that are throughout your libraries also.

Hmmm...I don't have any test.file files....

Link to comment
Share on other sites

diaz1510

Your library scan is completing, unlike before.

That's weird...my library scan completes every time it does one...when it shows the progress bar, it goes to 100% all the time...and always has...

Edited by diaz1510
Link to comment
Share on other sites

Still have the same issue on my side. See attached logs. Crashed at 7.23pm / 19.23.

 

This is being looked into, thanks. I believe it is already resolved on the beta channel in the event you need an immediate resolution.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...