Sluggishness in Logos Bible Software 6.0b SR-3 6.0.2.0079

Since installing the latest update I am getting the "rainbow" ball on my MacBook Pro (with 8GB Ram 2.67 GHz Intel Core i7) which has always been enough computing power. For this test I had nothing else running. I can simply try and scroll in an open Bible (or any window) and it brings the "rainbow" ball. Not sure what is causing this. I tried to do logs and I have a screen shot of what is open (which is a decent bit in Logos).

file:///Users/macbookpro/Desktop/LogosLogs.macbookpro.20150217-093202.zip (sample)

file:///Users/macbookpro/Desktop/LogosLogs.macbookpro.20150217-092448.zip

Let me know if things posted properly.

Find more posts tagged with

Comments

JT (alabama24)

Good job with the screen shot... the logs weren't attached right. Did you use the paperclip icon?

Your screenshot shows a LOT open, including a floating window. Is this normal for you? I also notice a link set. How much is linked?

Chad

https://community.logos.com/discussion/comment/697727#Comment_697727

I tried to use the paperclip for both a log and sample and it didn't open. I often use Duet Display with the floating window. But this also happened with a different layout which just has a couple of Bibles and a couple of devotionals. When you say "link set" I'm not sure what that refers too (sorry).

On the logs/sample - do I attach the .zip file? It won't attach for some reason.

Chad

https://community.logos.com/discussion/comment/697748#Comment_697748

Can I email the log files to someone - I get an "error" on the website when I try and upload. Any other options??

JT (alabama24)

https://community.logos.com/discussion/comment/697753#Comment_697753

LINK SET: the ability to link resources together based on common features (I.e. Versification). In your screen shot, the ESV is set to "link set A." Click on the resource menu (book cover) to find link sets

Logs: how large is the zip file? If it is unusually large, you might need to unzip it and upload individual files. Most important is the current logos.log file.

Chad

https://community.logos.com/discussion/comment/697757#Comment_697757

Ok - I have a few things linked - basically a number of the Bibles and then commentaries. Nothing really more than that.

The file is 21.4 MB so I'll try and upload some individual files. And there is another screenshot of the open log file - I believe this was the "sample" file. Thanks for the help.

0458.Logos.log

3250.LogosError-2.log

JT (alabama24)

https://community.logos.com/discussion/comment/697773#Comment_697773

Bump for Faithlife's attention.

Chad

https://community.logos.com/discussion/comment/697973#Comment_697973

Do I need to do something to bump it for Faithlife's attention?

JT (alabama24)

https://community.logos.com/discussion/comment/697975#Comment_697975

No. A "bump" just sends the post to the top of the forum, making it more visible. Your post (and this one) do the same thing as well.

Mike Binks

https://community.logos.com/discussion/comment/697975#Comment_697975

Do I need to do something to bump it for Faithlife's attention?

No! If you really want to get Faithlife's attention give them a ring.

I use Skype not being in the US.

Dave Hooton

https://community.logos.com/discussion/comment/697773#Comment_697773

The file is 21.4 MB so I'll try and upload some individual files.

Not sure what is the sample file but zip the sample.txt and logos.map files and email to support@logos.com quoting this thread

Alan Palmer (Logos)

https://community.logos.com/discussion/comment/697975#Comment_697975

Do I need to do something to bump it for Faithlife's attention?

I am not customer service. I am a developer. You have my attention. Please post a zip of all the logs created (instead of the individual log files). If you can't, feel free to email me directly (my email is easily deduced from my name... first.last@faithlife.com).

Having not seen your logs yet, allow me to offer some common things you might try:

Close panels you aren't using.
Disable visual filters. Not all VFs are created equal. "Links to open panels" is a known performance hog especially with a lot of panels open (you might try using the "Do not show in any resource" on this one).
Limit link sets. I don't see any obviously large link sets in your screenshot, but one might understand how scrolling could be slow if they had a link set with 100 resources. [:O]

JT (alabama24)

https://community.logos.com/discussion/comment/698207#Comment_698207

Please post a zip of all the logs created (instead of the individual log files). If you can't, feel free to email me directly (my email is easily deduced from my name... first.last@faithlife.com).

There is a reason he uploaded individual files:

The file is 21.4 MB so I'll try and upload some individual files.

Do you want him to email that?

Also, could you take a look at his second screen shot? Why do logs sometimes "collect"? Is that a bug? Is there a "clean up" process?

Alan Palmer (Logos)

https://community.logos.com/discussion/comment/698219#Comment_698219

The file is 21.4 MB so I'll try and upload some individual files.

Do you want him to email that?

Yes, that is what I asked him to do (and he has already done).

Also, could you take a look at his second screen shot? Why do logs sometimes "collect"? Is that a bug? Is there a "clean up" process?

I have no idea. I'll ask someone who may know and report back here.

JT (alabama24)

https://community.logos.com/discussion/comment/698224#Comment_698224

Yes, that is what I asked him to do (and he has already done).

Great! Thanks for helping him out. [:)]

I have no idea. I'll ask someone who may know and report back here.

Thanks for that too. This appears not infrequently where a forum member has a zip file too large to upload. On occasion, we end up seeing a screen shot and see that we have log-a-palooza.

Alan Palmer (Logos)

https://community.logos.com/discussion/comment/698219#Comment_698219

Also, could you take a look at his second screen shot? Why do logs sometimes "collect"? Is that a bug? Is there a "clean up" process?

Those wiser in the ways of Macintosh have informed me that the "log-a-palooza" (stealing your word, I like it) in this case is due to the fact that there was a time in our application's history that we were storing logs for "hangs" and "spins" because we thought they might be useful. It was determined later that this wasn't helpful to us and we stopped (the oldest file there was sometime last March). These files in particular can/should be deleted.

I'm not sure this particular situation is the only cause of "log-a-palooza", but if Mac users have these *.hang and *.spin logs they can safely be deleted. I hope that helps.

JT (alabama24)

https://community.logos.com/discussion/comment/698251#Comment_698251

Thanks Alan. [:)]