IMPORTANT: Proclaim 2.4 crashes on startup

Page 1 of 1 (10 items)
This post has 9 Replies | 0 Followers

Posts 13366
Forum MVP
Mark Barnes | Forum Activity | Posted: Mon, Aug 14 2017 8:39 AM

I just updated to Proclaim 2.4 and it crashes on startup, at least for me. Other users might want to hold off updating for now...

Application: Proclaim.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in async work
Stack:
at System.Environment.FailFast(System.String, System.Exception)
at Libronix.Utility.Threading.AsyncWorker+<>c__DisplayClass7_0.<DoStart>b__0(System.Threading.Tasks.Task)
at System.Threading.Tasks.Task.Execute()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.Task.ExecuteEntry(Boolean)
at System.Threading.Tasks.ThreadPoolTaskScheduler.TryExecuteTaskInline(System.Threading.Tasks.Task, Boolean)
at System.Threading.Tasks.TaskScheduler.TryRunInline(System.Threading.Tasks.Task, Boolean)
at System.Threading.Tasks.TaskContinuation.InlineIfPossibleOrElseQueue(System.Threading.Tasks.Task, Boolean)
at System.Threading.Tasks.Task.FinishContinuations()
at System.Threading.Tasks.Task.Finish(Boolean)
at System.Threading.Tasks.Task`1[[System.Threading.Tasks.VoidTaskResult, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].TrySetException(System.Object)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.Threading.Tasks.VoidTaskResult, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetException(System.Exception)
at Logos.Proclaim.Common.Model.AppStartupModel+<WorkOnlineWork>d__74.MoveNext()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at Logos.Proclaim.OurApp.InitializeAndRun(System.Collections.ObjectModel.ReadOnlyCollection`1<System.String>, Libronix.Utility.Threading.SingleInstanceManager)
at Logos.Proclaim.OurApp.Main(System.String[])

Posts 306
Brendon Marks (BCBC) | Forum Activity | Replied: Mon, Aug 14 2017 8:47 AM

It does not crash for me, I'm on Win 10.

Posts 13366
Forum MVP
Mark Barnes | Forum Activity | Replied: Mon, Aug 14 2017 9:01 AM

Brendon Marks (BCBC):

It does not crash for me, I'm on Win 10.

That's good news (for you at least!). I'm on Windows 10, too.

Posts 77
LogosEmployee
Brandon Adent | Forum Activity | Replied: Mon, Aug 14 2017 9:03 AM

Hi Mark, sorry you're having trouble.

Could you send us your log files please? We're unable to reproduce the problem here.

Thanks!

Posts 13366
Forum MVP
Mark Barnes | Forum Activity | Replied: Mon, Aug 14 2017 9:26 AM

Brandon Adent:

Hi Mark, sorry you're having trouble.

Could you send us your log files please? We're unable to reproduce the problem here.

Thanks!

Had exactly the same crash on a colleague's machine, which is also running Windows 10, but totally different spec to mine.

Sorry for not sending logs before. I was looking in the wrong folder and thought there weren't any.

4846.Proclaim Logs.zip

Posts 306
Brendon Marks (BCBC) | Forum Activity | Replied: Mon, Aug 14 2017 9:31 AM

I'm good on two different machines

Posts 77
LogosEmployee
Brandon Adent | Forum Activity | Replied: Mon, Aug 14 2017 9:48 AM

Thanks, Mark.

We can reproduce the problem. This affects users who are loading presentations that contain collapsed groups of service items. We'll be shipping an update shortly.

In the meantime, you can hold down CTRL (Win) or CMD key (Mac) to open Proclaim without a presentation loaded.

Thanks for your patience and for bringing this to our attention!

Posts 306
Brendon Marks (BCBC) | Forum Activity | Replied: Mon, Aug 14 2017 10:04 AM

My groups were not collapsed.

Posts 77
LogosEmployee
Brandon Adent | Forum Activity | Replied: Mon, Aug 14 2017 11:48 AM

We shipped an updated version this morning (2.4.0.004) that fixes this.

Sorry for the inconvenience!

Posts 13366
Forum MVP
Mark Barnes | Forum Activity | Replied: Mon, Aug 14 2017 1:32 PM

Thanks for the prompt fix! It's working for us now.

Page 1 of 1 (10 items) | RSS