When I enter <Mat 7.12> to search the whole library, it crashes.
0624.Logos4.log
6170.Logos4Crash.txt
3582.Logos4Error.log
2626.Logos4Indexer.log
Whilst this may not say Error 1887, your Error 4111 is the same crash that has plagued 5.0b beta!
Crash confirmed !
Crash confirmed
The screen shot only confirms that Logos crashed, but we need a crash log (as above) to determine if it has the same cause i.e Logos can crash for a variety of reasons. Are you running the beta version of Logos 5 (5.0b beta 1)?
I run LOGOS 4 which has never crashed before on my really powerfull PC (i7, 128 GB SSD, Win 7 Ultimate) . The problems are related to the latest update, especially the NT.
You need to report this in the Logos 4 Windows forum, unless you have the 4.6b beta. Either way you need to upload a full set of logs as per http://wiki.logos.com/Diagnostic_Logging
LOGOS 4.6b Beta 2 works flawlessly so far...
So the crash you confirmed earlier never happened? You are wasting time by not being more forthcoming.
The crash happened on Beta 1 and the screenshot represents Beta 1. I have downloaded Beta 2 afterwards and Logos 4 seems O.K. I am not sure how can I waste someone's time by reporting an unusual crash of Beta 1. If the crash has never happened then the screenshot is fake.
I could not reproduce the problem. It might have been solved in Beta 2 even though it does not say so in so many words in the release note.
I am not sure how can I waste someone's time by reporting an unusual crash of Beta 1. If the crash has never happened then the screenshot is fake.
If you go over our dialog I was asking you to submit some diagnostic logs so I could confirm that the crash you had was the same as the original poster (the screenshot doesn't show the search that the original poster used). I apologise for my confusion about the version of Logos you were running, but you ignored the request for logs despite my attempt to explain their importance.
It might have been solved in Beta 2 even though it does not say so in so many words in the release note.
You are right, this crash was solved in Beta 2. Thanks for pointing out that we missed adding it to the release notes! I have added it to the release notes for that beta.
