EasyPrint 3d Crash - Regional settings
Posted: Mon Feb 26, 2018 4:03 am
Hi
While slicing objects I'm always getting error on my PC - app crash.
I looked in event viewer and saw:
w System.Number.ParseDouble(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
w System.Convert.ToDouble(System.String)
w EasyPrint.view.CuraSlicer.GetProgressDetails(System.String)
w EasyPrint.view.CuraSlicer.ShowProgress(System.Object, System.Diagnostics.DataReceivedEventArgs)
w System.Diagnostics.Process.OutputReadNotifyUser(System.String)
w System.Diagnostics.AsyncStreamReader.FlushMessageQueue()
w System.Diagnostics.AsyncStreamReader.GetLinesFromStringBuilder()
w System.Diagnostics.AsyncStreamReader.ReadBuffer(System.IAsyncResult)
w System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
w System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
w System.IO.Stream+ReadWriteTask.System.Threading.Tasks.ITaskCompletionAction.Invoke(System.Threading.Tasks.Task)
w System.Threading.Tasks.Task.FinishContinuations()
w System.Threading.Tasks.Task.Finish(Boolean)
w System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
w System.Threading.Tasks.Task.ExecuteEntry(Boolean)
w System.Threading.ThreadPoolWorkQueue.Dispatch()
It made me thinking that there is a problem with regional settings (I'm in Poland so my decimal separator is , ).
Then run the same version on my VM with US regional settings - and works fine.
While slicing objects I'm always getting error on my PC - app crash.
I looked in event viewer and saw:
w System.Number.ParseDouble(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
w System.Convert.ToDouble(System.String)
w EasyPrint.view.CuraSlicer.GetProgressDetails(System.String)
w EasyPrint.view.CuraSlicer.ShowProgress(System.Object, System.Diagnostics.DataReceivedEventArgs)
w System.Diagnostics.Process.OutputReadNotifyUser(System.String)
w System.Diagnostics.AsyncStreamReader.FlushMessageQueue()
w System.Diagnostics.AsyncStreamReader.GetLinesFromStringBuilder()
w System.Diagnostics.AsyncStreamReader.ReadBuffer(System.IAsyncResult)
w System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
w System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
w System.IO.Stream+ReadWriteTask.System.Threading.Tasks.ITaskCompletionAction.Invoke(System.Threading.Tasks.Task)
w System.Threading.Tasks.Task.FinishContinuations()
w System.Threading.Tasks.Task.Finish(Boolean)
w System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
w System.Threading.Tasks.Task.ExecuteEntry(Boolean)
w System.Threading.ThreadPoolWorkQueue.Dispatch()
It made me thinking that there is a problem with regional settings (I'm in Poland so my decimal separator is , ).
Then run the same version on my VM with US regional settings - and works fine.