4.0b Beta 11 (4.02.3.6685) availableClosed
4.0b Beta 11 (v4.02.3.6685) is now available for testing.
For Release Notes, see http://wiki.logos.com/4.0b_Beta_11.
To upgrade from a previous beta, enter "update now" to begin downloading it. To install Beta 11 from scratch, see the notes and download link at http://community.logos.com/forums/t/8883.aspx
For 4.0b Beta 10 release notes, see http://community.logos.com/forums/t/11913.aspx.
Comments Closed
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
I bet your logs would tell. [;)] http://wiki.logos.com/Diagnostic_Logging
MacBook Pro (2019), ThinkPad E540
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
Did it produce a crash.txt file in your Logos Log Files folder? That is a new feature they added in Beta 10, so that regardless of whether you have diagnostic logging enabled, you can get some sort of report to give them to help track down what's causing the crash. Also of course it's good to try generating a log file as there might be more info in that which would help them. See http://wiki.logos.com/Diagnostic_Logging for how to generate the log files, and http://wiki.logos.com/Uploading_Logs for how to upload those log files (and crash.txt) as attachments here on a forum post.
Updated to the latest and crashes on startup. I did the <ctrl> trick and logged in blank. Upon loading the last workspace it crashes again. Did this twice. Tried loading blank and loaded another saved workspace and worked for a while and crashed again as I am typing. Not sure what is going on here.
Crash Log
Program Version: 4.0b Beta 11 (4.02.3.6685)
Windows Version: 6.1.7600.0
Time: 2010-02-18 15:51:24
Installed memory: 1,535 MB
Install path: C:\Users\Dewayne\AppData\Local\Logos4\System\Logos4.exe
Free disk space: 44,252 MB
Temp path: C:\Users\Dewayne\AppData\Local\Temp\
Free temp space: 44,252 MB
Error ID: 3746
Error detail: InvalidOperationException: Error reading postings. Document id out of range.
System.InvalidOperationException: Error reading postings. Document id out of range.
at Libronix.SearchEngine.PostingsFileSearchResultReader.ReadNextDocumentHeader()
at Libronix.SearchEngine.PostingsFileSearchResultReader.MoveToResult(SearchResultPosition posDesired, IWorkState workState)
at Libronix.SearchEngine.PostingsFileSearchResultReader.MoveToNextResult(IWorkState workState)
at Libronix.SearchEngine.OperatorOrSearchResultReader.MoveToResult(SearchResultPosition posDesired, IWorkState workState)
at Libronix.SearchEngine.OperatorOrSearchResultReader.MoveToNextResult(IWorkState workState)
at Libronix.SearchEngine.TemporaryFileSearchResultReader.Load(IWorkState state, SearchResultReader readerSource)
at Libronix.SearchEngine.QueryProcessor.CreateReaderForProcessedTerm(ExpandedTermListProcessedTerm termProcessed)
at Libronix.SearchEngine.ExpandedTermListProcessedTerm.CreateReader()
at Libronix.SearchEngine.QueryTreeConverter.Libronix.SearchEngine.IQueryNodeVisitor.Visit(TermQueryNode node)
at Libronix.SearchEngine.TermQueryNode.Accept(IQueryNodeVisitor visitor)
at Libronix.SearchEngine.QueryTreeConverter..ctor(QueryProcessor processor, QueryNode nodeRoot)
at Libronix.SearchEngine.QueryTreeConverter.ConvertQueryTreeToProcessorTree(QueryProcessor processor, QueryNode nodeRoot)
at Libronix.SearchEngine.QueryProcessor..ctor(IWorkState workState, IDocumentMetadataManager documentManager, FieldManager fieldManager, Lexicon lexicon, PostingsFileReader postingsReader, QueryNode nodeQueryRoot, QueryOptions options)
at Libronix.SearchEngine.QueryProcessor.ExecuteQuery(IWorkState state, IDocumentMetadataManager documentManager, FieldManager fieldManager, Lexicon lexicon, PostingsFileReader postingsReader, QueryNode nodeQueryRoot, QueryOptions options)
at Libronix.SearchEngine.Searcher.<>c__DisplayClass2.<ExecuteQuery>b__0()
at Libronix.SearchEngine.Searcher.LockIndexAndExecute[TResult](Func`1 fnLocked, Func`1 fnNotLocked)
at Libronix.SearchEngine.Searcher.ExecuteQuery(IWorkState state, QueryNode nodeQueryRoot, QueryOptions options)
at Libronix.DigitalLibrary.Searching.LibrarySearcher.GetSearchResults(IWorkState state, Func`1 fnCreateSearcher, QueryOptions options, IList`1 listResourceIds, Int32& nArticleCount, Int32& nHitCount, Int32& nResultCount)
at Libronix.DigitalLibrary.Searching.LibrarySearcher.DoRunSearch(IWorkState state, QueryOptions options, IList`1& listMainResults, IList`1& listSupplementalResults)
at Libronix.DigitalLibrary.Searching.LibrarySearcher.SearchAndMergeResults(IWorkState state, QueryOptions options, IComparer`1 comparer, SearchResultSummary& summary)
at Libronix.DigitalLibrary.Searching.HitsByResourceLibrarySearcher.GetResults(IWorkState state, Int32 startIndex, Int32 resultCount, SearchResultSummary& summary)
at LDLS4.Panels.VisualFilterPanel.VisualFilterDocumentUserVisualFilterManager.FilterCache.<RefreshWork>d__b.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution()
at Libronix.Utility.Threading.AsyncAction.Continue()
at Libronix.Utility.Threading.ThreadPoolAsyncAction.<Start>b__0(Object )
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(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)
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”
Error detail: InvalidOperationException: Error reading postings. Document id out of range.This indicates that corruption was introduced at some time from merging indexes, and the 'rebuild index' command should fix this crash.
Melissa
Melissa, there seem to be a lot of users on the forum with corrupted indexes. Is the next release going to handle the corruption appropriately? Or will we still be getting users with crashing indexers?
MacBook Pro (2019), ThinkPad E540
Error detail: InvalidOperationException: Error reading postings. Document id out of range.This indicates that corruption was introduced at some time from merging indexes, and the 'rebuild index' command should fix this crash.
Melissa
Two hours into the rebuild. I will let you know if it fixes it. Thanks.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”
Two hours into the rebuild. I will let you know if it fixes it. Thanks.
It is working great now. Thanks.
“... every day in which I do not
penetrate more deeply into the knowledge of God’s Word in Holy Scripture
is a lost day for me. I can only move forward with certainty upon the
firm ground of the Word of God.”
4.0b Beta 11 (v4.02.3.6685) is now available for testing.
Installed and working without problems.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
4.0b Beta 11 (v4.02.3.6685) is now available for testing.
Downloaded, installed and is running fine.
Lenovo P72: Intel 8th Gen i7-8750H 6-core, 32GB RAM, 2TB HDD + 1TB Sata SSD, 17.3" FHD 1920x1080, NVIDIA Quadro P600 4GB, Win 10 Pro
Downloaded, installed and is running fine.
Ditto
After upgrading to Beta 11, on every start of the beta I get an additional update available downloading message. It comes and goes very quickly, so I am not sure the size of this download. It doesn't appear to do anything. It is very small... Looks like 25.6K. This also appears with update now command.
Does anyone else see this?
No, but if you post your logs, we could see what the resource was.
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!
Part of the log file is below with the log file for the session attached, now I see the resource but don't know who to resolve this.
2010-02-19 16:50:58.0638 5 Info UpdateManager No more resource file info objects retrieved; checking unknown resource status.
2010-02-19 16:50:58.0798 12 Info UpdateManager Re-attempting download of 1 resources marked as failed: LLS:LEXSGGLOSSARY
2010-02-19 16:50:58.0938 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.0938 12 Info UpdateManager Resource 'LLS:LEXSGGLOSSARY' is out of date.
2010-02-19 16:50:58.1198 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.1408 12 Info UpdateManager There are existing New or Postponed updates; raising event.
2010-02-19 16:50:58.1408 12 Info UpdateManager Starting Update Manager processing in 06:00:00.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are available.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are set to download automatically; starting download.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Starting download of 1 updates.
Part of the log file is below with the log file for the session attached, now I see the resource but don't know who to resolve this.
2010-02-19 16:50:58.0638 5 Info UpdateManager No more resource file info objects retrieved; checking unknown resource status.
2010-02-19 16:50:58.0798 12 Info UpdateManager Re-attempting download of 1 resources marked as failed: LLS:LEXSGGLOSSARY
2010-02-19 16:50:58.0938 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.0938 12 Info UpdateManager Resource 'LLS:LEXSGGLOSSARY' is out of date.
2010-02-19 16:50:58.1198 12 Info UpdateManager Checking for resources with 'Unknown' status.
2010-02-19 16:50:58.1408 12 Info UpdateManager There are existing New or Postponed updates; raising event.
2010-02-19 16:50:58.1408 12 Info UpdateManager Starting Update Manager processing in 06:00:00.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are available.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Updates are set to download automatically; starting download.
2010-02-19 16:50:58.1408 1 Info LDLS4.AppModel Starting download of 1 updates.
It sounds like the same issue a user was getting in this thread http://community.logos.com/forums/p/8136/64605.aspx#64605
Sounds like this is just about to launch...[:D]
I would guess RC 1 is just around the corner... [:)]
soon and very soon I think, for me its 95% there, all I really miss are my sentence diagrams...
I say 95% 'cos I dont expect my notes gripes ever to be fixed... otherwise its about 90%
Never Deprive Anyone of Hope.. It Might Be ALL They Have
I think sentence diagrams are probably going to be in 4.0c, which has already been under development for a while as a few developers remain on 4.0b fixing bugs. Bradley hints we might getting the first beta of 4.0c before March 16.
Sure would love to see the file menu organized before it does. All those note files sure gum things up.
Pastor, North Park Baptist Church
Bridgeport, CT USA
I hope not. Still waiting on the text to speech bug to be fixed. Pressing the down arrow key stops the speech