REPRODUCIBLE CRASH: L9: Searching for text that appears within a Timeline resource
Here are the steps that cause this repeatable crash:
0. Make sure the last time you did a Basic search the results were sorted by "Ranked" so it will default to this again.
1. Open Logos
2. Open a Search Tab for a Basic Search, All Text in All Resources.
3. Search for any phrase that occurs in any of the timeline resources, in quotation marks. For example "Tatian the Assyrian" (which is in Church History Timeline), or "James Moffatt Bible" or "Douay-Rheims" (which are in "English Bible Versions Timeline").
Wait a few seconds
Crash
Logs attached: 3301.Logos20220801.zip
NOTES:
I've tried it with opening to a blank layout by holding down CTRL too, and same crash.
It appears not to happen with searches for a single word, only for a phrase in quotation marks.
And it doesn't happen when the search results are sorted by Resource, only Ranked.
Comments
-
bump for attention which is typical for Saturday 4
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Hi Rosie,
Thanks for reporting this crash. I'll get a case written up.
0 -
Hi Rosie,
Thanks for reporting this crash. I'll get a case written up.
Thanks. I would love to hear if you were able to reproduce it following my steps. After that I'll trust it to your bug database and hope it will get fixed eventually...
0 -
Hi Rosie,
Thanks for reporting this crash. I'll get a case written up.
Thanks. I would love to hear if you were able to reproduce it following my steps. After that I'll trust it to your bug database and hope it will get fixed eventually...
Hi Rosie,
I was able to reproduce almost the same way. I had to expand the results for the resource before it would crash. However, I did compare the crash log that was generated when I reproduced it and they matched.
0 -
I was able to reproduce almost the same way. I had to expand the results for the resource before it would crash. However, I did compare the crash log that was generated when I reproduced it and they matched.
Thanks. Somehow there's always something satisfying about finding a crashing bug. It means I found something others missed. I hope it is deemed worthy of fixing and isn't too hard.
0 -
I was able to reproduce almost the same way. I had to expand the results for the resource before it would crash. However, I did compare the crash log that was generated when I reproduced it and they matched.
Thanks. Somehow there's always something satisfying about finding a crashing bug. It means I found something others missed. I hope it is deemed worthy of fixing and isn't too hard.
Hi Rosie,
This has been fixed in 9.16.
0
