[resolved] BUG: Logos 6 Search Crashes on Surface 3 When Changing the Scope/Domain of Searches Acros

I would like to report reoccurring crashes that I have been experiencing while performing searches on my new Surface 3. I am currently running Logos 6.2 SR-1
6.2.0.0043 and Windows 8.1 with all Windows updates installed.

I have log files illustrating three different but related crashes. In all three crashes, I first loaded Logos 6 with a blank layout and with logging enabled. I then opened the Lexham Hebrew Bible (LHB) and a search panel—not necessarily in that order—and sent all searches to that panel. I then performed one or more searches before performing a final search that crashed Logos 6. The final search seems to have always included a broadening or narrowing of the search scope (e.g., in the case of the first two crash logs, from searching in the LHB to searching "Everything"; and in the case of the last crash log, from searching in "Everything" to searching the LHB).

Thus, in the first two crashes, I first performed various searches from the right-click menu in the LHB (e.g., lemmas, people, things, senses, and morphology), then I performed a search in "Everything," which lead to a crash. The first crash occurred around 1:56 p.m. (CST) and involved right-click search for <Bezalel (craftsman)> in "Everything." The second crash occurred around 2:04 p.m. and involved a search from my previous search history for (host, court, council, angel) WITHIN {Milestone <Gen 1.26-27>} in "Everything."

For my third search, I began with the same search that caused the second crash: (host, court, council, angel) WITHIN {Milestone <Gen 1.26-27>} in "Everything." This time it worked. But when I followed it up with a lemma search from the right-click menu in the LHB, Logos 6 crashed for a third time, this time at 2:14 p.m. I believe the final search was <Lemma = lbs/he/זָהָב>.

The log files are attached below. I hope this information helps!

1122.Logos 6 Crash 1 - Biblical Person Search for Bezalel in Everything.log

6318.Logos 6 Crash 2 - Milestone Search Gen 1.26-27 in Everything.log

1220.Logos 6 Crash 3 - Search for Lemma in LHB.log

Comments

Sort by:
1 - 1 of 11

    Thanks for the excellent descriptions, Adam

    Each log ended suddenly without an indication of a crash. Please post logs from the Windows Event Viewer at the times you mention.

    Also upload the Logos Error log.

    Dave
    ===

    Windows 11 & Android 13

    Thanks for the excellent descriptions, Adam

    Each log ended suddenly without an indication of a crash. Please post logs from the Windows Event Viewer at the times you mention.

    Also upload the Logos Error log.

    Dave, thank you for your help. The Wiki instructions were very clear and helpful as well.

    My Windows Event Viewer logs include .NET Runtime Errors, Application Errors, and Windows Error Reporting for each of the three crashes. I am also including the Logos Error log as you requested. It appears that the any errors reported in there are from either today (05/12/2015) or from the day before I logged and reported the three crashes above (05/10/2015).

    5751.Event Viewer Logs - Logos 6 Search Crashes on Surface 3 When Changing the Scope of Search.txt

    3386.LogosError.log

    My Windows Event Viewer logs include .NET Runtime Errors, Application Errors, and Windows Error Reporting for each of the three crashes.

    This article discusses problems with the .Net Framework.

    https://www.logos.com/support/logos5/windows/dotNET 

     

    My Windows Event Viewer logs include .NET Runtime Errors, Application Errors, and Windows Error Reporting for each of the three crashes.

    This article discusses problems with the .Net Framework.

    https://www.logos.com/support/logos5/windows/dotNET 

    Thanks, Tommy. No success yet.

    I don't know if it helps matters at all, or if it will help someone in the future, but I will add that I do not encounter crashes while searching, when

    A) I maintain the same search scope between searches OR

    B) I send new searches to new search panels, rather than sending all searches to the same search panel.

    As I have the time, I'll have to go over those instructions that you linked to again to make sure there is nothing I missed. Otherwise, I can try contacting Microsoft as well.