BUG: Only way to stop a long search is to Force Quit Logos
Accidentally triggered a morph search for lemma:ο@DGSM in NA27 - been running for 3 mins now and no way to stop. Had to force quit Logos. This has happened a few times, when I search for something that returns a large number of hits. Each time I have to force-quit Logos, meaning my workspace is not remembered, etc. Not pretty.
Some means of stopping a long-running search should be provided. Simply showing the "spinning pizza of death" isn't appropriate behavior.
The irony is that the search results window showed "4072 results in 1623 verses (0.34 sec)" almost instantaneously, and then proceeded to hang while, I assume, rendering the results. Thus, the search part is probably fine, but the UI part is in need of some serious attention.
Comments
-
Logos devs might want to look into why a hanging gdb process is spawned when these hangs occur, as shown below:
stuart@Macbook $ ps aux | grep gdb
stuart 27367 0.0 3.0 2708132 248328 ?? S 8:31am 0:03.37 /usr/libexec/gdb/gdb-i386-apple-darwin -batch -x /tmp/mono-gdb-commands.bVzfLb
As I've pointed out before, the only way to get rid of the "dead" windows after a force-quit is to open a terminal and kill the hanging gdb process - not something the average user will know how to do. Interestingly, I've yet to receive any acknowledgement from the Logos devs about the gdb issue...
0 -
This may be related to the issue reported here: http://community.logos.com/forums/t/27711.aspx which development has been working on. The same search you describe crashes the app on my system.
0
