Repeatable Crash on 5.2: System.ArgumentNullException: Value cannot be null.
I got the following message when running a BWS: Unhandled exception: System.ArgumentNullException: Value cannot be null. I get it when I run a BWS on the English word 'see'.
2013-11-17 08:39:01.0081 1 Error OurApp Unhandled exception: System.ArgumentNullException: Value cannot be null.
Parameter name: description
at Libronix.DigitalLibrary.Guides.Sections.ResourceLink.Create(ResourceMilestoneRange range, String resourceTitle, String description, Boolean isStarred)
at Libronix.DigitalLibrary.Guides.Sections.DefinitionSection.<DoWork>b__16(<>f__AnonymousType9`3 x)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Libronix.Utility.EnumerableUtility.ToReadOnlyCollection[T](IEnumerable`1 seq)
at Libronix.DigitalLibrary.Guides.Sections.DefinitionSection.<DoWork>d__43.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution(Object unused)
at Libronix.Utility.Threading.AsyncAction.ContinueCallback(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(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.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim)
at LDLS4.OurApp.Main(String[] astrArgs)
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
I can reproduce this following your link
0 -
-
0
-
Interestingly, I couldn't reproduce by clicking the link and invoking L5 with it. (I speculated it might have to do with the aspect that you invoke language en-GB, while I'm currently running in German).
When I clicked again for the running app, it didn't crash either - nor with typing see into the bws field. It crashed when I tried to open the "definitions" field. Logs attached.
Have joy in the Lord!
0 -
NB.Mick said:
I couldn't reproduce by clicking the link and invoking L5 with it.
When I clicked the link in Mark's post, L5 become the active application, but BWS was not opened. Figured that was a Mac-thing. Pasted the link into the command field, and BWS opened to see without any incident. That is when I made the previous post.
NB.Mick said:It crashed when I tried to open the "definitions" field. Logs attached.
After reading Mick's post, I tried the again initiated BWS from the command field. Then, I clicked on the definitions field, and was rewarded with a crash. Logs follow.
7851.LogosLogs.jackcav.20131117-151830.zip
So, it is not a Windows-only bug [:(]
0 -
I will create a case for Development.
0 -
This issue should be fixed in 5.2 SR-2.
0 -