Search hangs requiring force quit
MBP Ventura L10 stable M1
I ran a search from the context menu on my preferred bible, then ran an all search on the same word from the context menu and L10 froze with the spinning beach ball. Had to force quit. Logs below:
Comments
-
Me too - this happens every time I try to search "Bible" spinning wheel and have to force quit.
0 -
-
Sorry replied to the email!
Hello, Thank you for such a quick response!
Step by step :--- Open Logos (iMac OS Ventura) – open NKJV – in tool bar click on search – (Home, Library, Search) it opens up the search box
All – Bible – Books - Media etc. – as soon as I click on Bible the spinning wheel begins – and I have to force quit to stop it.
It has been doing this for a couple of weeks – but I can still search in the NKJV – but it is not as good.
Hope this is easy to follow – I do have Logos on two computers and it is only this one that search crashes. Both Macs and same software and OS
Appreciate any suggestions, must say I think Logos 10 is an amazing step forward – I have been using Logos since floppy disc days!
Blessings, Graeme
0 -
Graeme--I don't know exactly what's happening on your end, but perhaps we can get you 'unstuck' on that machine by starting the app up while holding the 'command' button. Will you give that a try and let me know if that helps?
0 -
John--We'll probably have more follow up questions, but for now I'm wondering, is this consistently happening for you, or was it a one-time deal? i.e. do you get the same behavior if you follow the same steps (i.e. from the context menu) for the same term, etc?
0 -
Hi Ronny,
I cannot find an exact pattern, but it does happen when I have been doing lots of different kinds of searches (bible, book all etc.) when the search box has "send searches here" selected, so it is repopulating the same search pane. I think the search box has difficulty changing the type of search perhaps if different searches are run from the context menu. When it does freeze there is nothing to do but force quit. It reopens fine.
Maybe difficult to tie down if the logs I attached don't show anything. I will keep you informed. I appreciate your follow up.
0 -
-
0
-
I couldn't replicate.
13.0.1 on Apple Silicon, running 10 beta 4.
L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
Open search box with send searches here selected. Run a search on Rahab and open Josh 2.1. In the context menu for Josh 2.1 click on Rahab and run a Factbook. At the bottom of Factbook there is a search for Rahab link, click on it and L10 freezes.
Didn't take me long. My Verbum is fast on bug detection. Image one, is after I started the Rehab search. Just to make sure, I tried different Bibles (zippo results), and then a Books search (no issues; thousands). Then to lock up Verbum, I went back to the Bible search (same panel). Locked and no entry text box. Mac M1 Ventura, Verbum .240.
0 -
DMB thanks for the verification.
0 -
John and Graeme--Random question; could you guys tell me what you have set for 'Program Scaling' and 'Content Scaling' in your program settings?
0 -
John and Graeme--Random question; could you guys tell me what you have set for 'Program Scaling' and 'Content Scaling' in your program settings?
Good question:
Content is 120% and scaling is 90%
0 -
I changed to 100% and 100% for both settings and the problem appears to have gone away. I do prefer the other settings, but will leave it until you get the matter resolved.
0 -
Hi Ronny, scaling was 100% and 110% -- changed both to 100% -- problem solved!
Well done thank you very much.0 -
Reset mine from 110%/110% to both 100%.
Rahab's back in the Bible! Whoo hoo! I wonder what program scaling did?
Also tthe flakey Library filter bug is now behaving. I wonder how many more bugs are impacted. The top menu is stable, so far. Hope, hope.
0 -
Scaling can create some interesting bugs...
0 -
Glad it was as simple as changing the scaling; sorry for the trouble. This is a Ventura-specific issue we discovered recently. Once you upgrade to 10.1, adjust your scaling back to your desired settings and you should be good to go; let us know if issues persist.
Thanks,
-Ronny
0