Bug: Crash in 4.0a on start

Here are the relevant lines from logs
2009-12-29 10:01:24.9699 14 Info HomePage.MediaHomePageItemProvider Cached xps C:\Users\Mark Barnes.EMW\AppData\Local\Logos4\Data\vqzpi4x1.qsx\HomePage\2009-12-29\wpjoq5cv.dnh
2009-12-29 10:01:27.9664 14 Info HomePage.MediaHomePageItemProvider Cached blank xps C:\Users\Mark Barnes.EMW\AppData\Local\Logos4\Data\vqzpi4x1.qsx\HomePage\2009-12-29\Xps\jqxzvwwd.cno
2009-12-29 10:02:10.7230 14 Error OurApp Unhandled exception: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at Libronix.Utility.Windows.BitmapSourceUtility.CreateThreadSafeCopy(BitmapSource sourceBitmap)
at Libronix.DigitalLibrary.Resources.Media.MediaResourceUtility.<GetResourceImage>b__3(BitmapSource x)
at Libronix.Utility.IfNotNull.IfNotNullExtensionMethod.IfNotNull[T,U](T t, Func`2 fn)
at Libronix.DigitalLibrary.Resources.Media.MediaResourceUtility.GetResourceImage(Resource resource, String strMediaName, BitmapSizeConstraint constraint)
at Libronix.DigitalLibrary.Resources.Media.MediaResourceUtility.GetResourceImage(Resource resource, String strMediaName)
at LDLS4.HomePage.Items.MediaHomePageItemProvider.GetImageHomePageItem(String strResourceTitle, ResourceMediaReference reference, Double fInclusiveMinRank, Double fExclusiveMaxRank, ReadOnlyCollection`1 collTags)
at LDLS4.HomePage.Items.MediaHomePageItemProvider.GenerateItem(ResourceMediaReference reference, Double fInclusiveMinRank, Double fExclusiveMaxRank, ReadOnlyCollection`1 collTags)
at LDLS4.HomePage.Items.MediaHomePageItemProvider.FindMedia(Query query, Double fInclusiveMinRank, Double fExclusiveMaxRank, IWorkState state)
at LDLS4.HomePage.Items.MediaHomePageItemProvider.GetItem(IEnumerable`1 seqResourceIds, Double fInclusiveMinRank, Double fExclusiveMaxRank, Double fNoReferencesInclusiveMinRank, Double fNoReferencesExclusiveMaxRank, IWorkState state, MediaTagKind[] aTags)
at LDLS4.HomePage.Items.MediaHomePageItemProvider.GenerateItemsCore(IWorkState state)
at LDLS4.HomePage.Items.HomePageItemProvider.GenerateItems(IWorkState state)
at LDLS4.HomePage.HomePageViewModel.<>c__DisplayClass64.<GenerateItemsWork>b__4a(Object prov)
at Libronix.Utility.Threading.DelegateAsyncWorkItem.<ExecuteCore>b__0(Object o)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at Libronix.Utility.Threading.DelegateAsyncWorkItem.ExecuteCore()
at Libronix.Utility.Threading.AsyncWorkItem.Execute()
at Libronix.Utility.Threading.ThreadPoolAsyncWorkItem.<StartCore>b__0(Object o)
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
It was checking for updates whilst all this was going on.
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
-
Mark Barnes said:
Unhandled exception: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
Running low on RAM/hard disk space (for swap file)?
0 -
No, 2Gb RAM, with few other applications loaded, and over 100Gb HDD space. I've had this error on both my machines, during major update checks (I think after upgrading to 4.0a). Watching the logs, each time Logos seems to get further, so you just keep restarting and eventually it will work.
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!
0