Two Indexers...Again
A few weeks ago Logos opened a second indexer while it was indexing and then later opened a third. This resulted in Logos crashing and not reopening. This meant I had to spend almost an hour on the phone with tech support. They ended up having to delete the index file, and reindex my entire library (3,500-plus volumes) which took several hours.
Now, Logos has done it again. One indexer opened, then another. One has run to completion but the other is still in the menu bar but it is greyed out and when I float my pointer over it, I get the spinning beach ball of death.
Logos is a great program when it works but it is becoming more and more like a Microsoft product in that I spend more time dealing with the program than I do simply using the product to do my work.
My Mac runs just fine except when Microsoft Office and Logos are running, then I might as well be back on a PC.
Comments
-
This happens due to a limited amount of shared cache on the Mac. Rebooting the machine should prevent this.
0 -
In 5.1, you can use Tommy's workaround. In 5.1a, we will be improving the detection of whether the Indexer is already running (to prevent this problem).
0 -
I'm skeptical about your claim that rebooting should prevent this. The last time I had two and rebooted Logos opened a third and crashed every time I tried to open it. Are you saying that I should reboot before downloading updates etc.? Because that isn't something I should have to do to update an app.
0 -
Michael R. Jones said:
Because that isn't something I should have to do to update an app.
I haven't had this issue for a while… and rebooting does sound unusual for us Mac users. [:)]
For clarification though, when the indexer appears, you aren't updating the "app," but rather the resources.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
This is not normal behaviour for Macs, or for Logos running on a Mac. Indexing should only be a one-time thing for new or updated resources and I have never seen more than one indexer running.
As for the "limited amount of shared cache on the Mac" — hmmm, I'm not totally buying that. If Logos had/caused such an issue with respect to a common aspect of Macs then the forum would be running red hot with people complaining.
If it is related to Logos using shared cache then it may/would be more likely that there is an issue with your specific Mac/Logos installation.
Some Mac things you can try to correct the issue:
- Check and repair permissions: http://macs.about.com/od/backupsarchives/ss/diskbackup_3.htm
- Clear the dynamic link editor cache: http://macs.about.com/od/usingyourmac/qt/Fix-Spod-How-To-Fix-A-Spinning-Pinwheel-Of-Death.htm
- Some other things: http://reviews.cnet.com/8301-13727_7-20025628-263.html?tag=contentMain;contentBody
STANDARD DISCLAIMER: All of the above will 'clean out' system things, they are general commands which will reset, not change, things on your Mac. However with any command you run on your system please understand it is at your risk. It is highly advisable not to be running any applications when you do any of these tasks.
Give the above a go and see how Logos runs afterwards — hopefully your Mac will be happier with Logos.
It always pays to remember that Logos is not a 'pure' Mac application — not that that means it won't run, obviously it does, but that, speaking figuratively, OS X may look at Logos running and say "you're obviously not from around these parts...".
"I want to know all God's thoughts; the rest are just details." - Albert Einstein
0
