Logos Indexer is Causing my Macbook Pro fan to run constantly at a high speed.

Page 1 of 1 (11 items)
This post has 10 Replies | 1 Follower

Posts 4
James Wright | Forum Activity | Posted: Fri, Mar 11 2016 7:07 AM

The Logos indexer is running at nearly 300%, I don't know how that's possible, of my RAM and is causing the fan to run very loudly on my Mac Book Pro. Any ideas? If I go into the Activity Monitor I can shut it off, but to run the indexer my fan constantly runs. 

Posts 21725
Forum MVP
Graham Criddle | Forum Activity | Replied: Fri, Mar 11 2016 7:10 AM

Hi James - and welcome to the forums

Sorry to hear you are having problems.

There is currently a bug affecting some Mac users which results in repeated indexing. It is possible you are experiencing the same thing.

I believe Faithlife are hoping to ship a fix later today so it may be worth holding back from using Logos until that is available and you have installed it.

Although the bug, as I understand it, results in repeated reindexing and shouldn't affect how much of the system is used when indexing so it may be something else. Hopefully other Mac users - particularly those who have experienced this problem - will be able to comment further.

Graham

Posts 1526
Forum MVP
Levi Durfey | Forum Activity | Replied: Fri, Mar 11 2016 7:15 AM

There's another thread here about this issue: https://community.logos.com/forums/t/123602.aspx 

I read that it's a complex problem that won't be fixed in the 6.10 SR-1 release, but in the 6.10 SR-2 release.

See here https://community.logos.com/forums/p/123764/809156.aspx#809156 

and here https://community.logos.com/forums/p/123926/809363.aspx#809363 

Posts 1526
Forum MVP
Levi Durfey | Forum Activity | Replied: Fri, Mar 11 2016 7:18 AM

It would be helpful for Faithlife if you post your logs...see my signature line for instructions on how to post logs for mac.

Posts 4
James Wright | Forum Activity | Replied: Fri, Mar 11 2016 7:25 AM

Thank you. This began last night, thankfully I learned enough about how to shut down indexing, at least for now.

Posts 4
James Wright | Forum Activity | Replied: Fri, Mar 11 2016 7:30 AM

How were you able to downgrade to 6.9?

Posts 21725
Forum MVP
Graham Criddle | Forum Activity | Replied: Fri, Mar 11 2016 7:36 AM

James Wright:

How were you able to downgrade to 6.9?

Downgrading to 6.9 would require deleting all of your downloaded resources and downloading them again.

If at all possible I recommend waiting until a fix is available or another update from Faithlife

Posts 1526
Forum MVP
Levi Durfey | Forum Activity | Replied: Fri, Mar 11 2016 7:38 AM

James Wright:
The Logos indexer is running at nearly 300%, I don't know how that's possible

It possible because you have a Quad-Core processor (4 cores). Each core can run to 100%, for a total of 400%.

James Wright:
How were you able to downgrade to 6.9?

Basically, you have to remove absolutely everything and reinstall (using the 6.9 SR-1 engine). I had a Time Machine backup of my resources, so I didn't have to redownload all my resources. See here for more information: https://wiki.logos.com/mac_troubleshooting#Want_to_downgrade_from_Beta_to_Stable 

I am currently back on 6.10, but the reindexing hasn't bothered me possibly because I've kept "Use Internet" off (I suspect that any new resource update triggered a full reindex).

Posts 27446
Forum MVP
JT (alabama24) | Forum Activity | Replied: Fri, Mar 11 2016 8:03 AM

Graham Criddle:

If at all possible I recommend waiting until a fix is available or another update from Faithlife

I concur. The fix is anticipated today, but delays are possible 

OSX & iOS | Logs |  Install

Posts 1471
Angela Murashov | Forum Activity | Replied: Fri, Mar 11 2016 10:57 AM

alabama24:

Graham Criddle:

If at all possible I recommend waiting until a fix is available or another update from Faithlife

I concur. The fix is anticipated today, but delays are possible 

This should be fixed in 6.10 SR-2. Please let us know if you are still having this issue after the update.

Posts 4
James Wright | Forum Activity | Replied: Fri, Mar 11 2016 4:27 PM

I think that fixed it. I needed to reboot the computer first, but it got it.

Page 1 of 1 (11 items) | RSS