search

Wulf2k / DaS-PC-MPChan

77 stars 30 forks source link

remote name could not be resolved crash after long runtime #107

Closed metal-crow closed 8 years ago

metal-crow commented 8 years ago

Leaving DSCM running for extended periods of time (~12 hours), leads to the follow exception

System.Net.WebException: The remote name could not be resolved: 'chronial.de'
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
   at System.Net.WebClient.DownloadBitsResponseCallback(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 DSCM.MainWindow.VB$StateMachine_43_updateOnlineState.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)

Minor bug for most people, but annoying for Dark-Souls-PvP-AI.

Chronial commented 8 years ago

This is probably an issue with your internet connection. Every 10 minutes, DSCM updates the onlinestate of your recent nodes. This error is thrown if you internet connection is not working during one of these checks.

That being said, that should not cause a crash like this.

Chronial commented 8 years ago

Thanks for reporting.