CPU usage bug?

https://community.logos.com/discussion/comment/462821#Comment_462821

Logos was not indexing.

Is anybody else having this kind of problem?

Personally, have never seen this type CPU usage except when L5 is indexing.

Nick Harris

Yep, it seems like i "force quit" a few times per week. The fan on my computer turns off right after I quit Logos. I have a brand new Mac so I don't think that's the problem.

Mark Nigro

https://community.logos.com/discussion/comment/467344#Comment_467344

Until yesterday, this hadn't happened to me. However, I can recall exactly what I was doing just prior to setting off the fans. In a sprint of curiosity I began adding a few resources in my pane and then switching through some parallel resources looking for something specific. After switching through about 6 to 10 parallel resources, my fans kicked in and would not calm down. I also noticed that 'syncing' would not finish. Quitting Logos worked but the final exit screen "Updating and Syncing Documents and Settings" would not go away. I ended up having to force quit.

Thomas Ball

https://community.logos.com/discussion/comment/467373#Comment_467373

Fans turning on is not necessarily a bug. Logos is a big program (despite what some seem to think), and big programs cause heat and the fan is there to protect your computer.

After switching through about 6 to 10 parallel resources, my fans kicked in and would not calm down. I also noticed that 'syncing' would not finish.

I could see this kicking the fans on until the computer feels the computer has cooled down enough.

uitting Logos worked but the final exit screen "Updating and Syncing Documents and Settings" would not go away. I ended up having to force quit.

This, however, should not happen. Can you replicate this behavior?

the Rev

I'm also getting the same CPU problem running Logos 5. When I quit logos CPU usage drops to normal. This is a really big problem because it makes my iMac extremely hot 70 degrees celsius. This is a relatively new problem. Please help us

https://community.logos.com/discussion/comment/467482#Comment_467482

This is still a problem. Here are my logs and my most recent screen capture with the exceptionally high processor usage.8623.LogosLogs TIMOTHY HANKINS 20130304-115609.gz

https://community.logos.com/discussion/comment/468557#Comment_468557

When it gets like this I have to force quit, exiting hangs on the synch window without releasing any of the processor that it is using. Here is another after forcing quit and reopening the same layout and working for a few minutes:

Mike

https://community.logos.com/discussion/comment/468411#Comment_468411

Computers are designed to cool themselves automatically when operating at capacity, then clock-back the processor if it gets too hot. So while it may be very warm, if the hardware, fans and drivers are functioning correctly, and it was well designed to start with, high CPU load and elevated temperatures should not be a problem. Occasionally, the hardware may malfunction, or the software/drivers may not be operating the fans correctly which can lead to over-heating, but most current processors will detect this and automatically clock back and ultimately shut down before damage occurs. This is a problem with the hardware or driver and should be discussed with the manufacturer.

Ultimately, we would expect Logos to use whatever system resources are available to perform resource-intensive tasks as quickly as possible, especially while indexing. This will result in high CPU load, and higher than idle temperatures, but shouldn't cause hardware damage if the computer is functioning correctly.

However, if you are concerned that Logos is not operating properly, we may be able to collect some specific data to troubleshoot. You'll find new instructions at www.logos.com/support/logos5/mac/logging to collect this data (step 4). If the files are too large to attach, please submit them by email.

https://community.logos.com/discussion/comment/468562#Comment_468562

Mike, thank you for the response.

Computers are designed to cool themselves automatically when operating at capacity, then clock-back the processor if it gets too hot. So while it may be very warm, if the hardware, fans and drivers are functioning correctly, and it was well designed to start with, high CPU load and elevated temperatures should not be a problem. Occasionally, the hardware may malfunction, or the software/drivers may not be operating the fans correctly which can lead to over-heating, but most current processors will detect this and automatically clock back and ultimately shut down before damage occurs. This is a problem with the hardware or driver and should be discussed with the manufacturer.

- As a former helpdesk technician and network engineer, I can appreciate your simple explanation. My concern is not for my hardware so much as the sometimes frustrating loss of performance that I experience while the processor is running this high.

[quote]

- if you will take a moment to refresh your memory with regards to the information previously posted, you will note that my initial post was in part because logos isn't indexing while I am having this happen. In fact, Logos is pretty much sitting idle. I am not performing any searches nor do I have any linked books that are trying to keep up with each other. I do not have any clausal diagrams open, both of which can sometimes eat up resources. I have had this happen with multiple layouts, including one I rebuild from scratch in case there is a problem with layout corruption. I am not compiling personal books. I am not using any of the Logos tools whatsoever. I am just reading a few commentaries and a couple books and following embedded scripture links to an open Bible. As shown by my second screen capture, this is normally done with nearly no processor usage.

[quote]

Please note that my previous post did have my most current set of logs. I leave logging running because of intermittent issues. I used logos log scribe to gather and compress the log files.

This problem has started only within the last couple updates. Off the top of my head I would guess that logos is scaling to handle some momentary intensive task and some piece of code is written such that it fails to scale back down, but i recognize that tech support guys with a hardware background frequently point fingers at the coders, so that may just be my instincts leading me astray.

Thank you again for your time in looking into this matter.

-Tim

Mike

https://community.logos.com/discussion/comment/468599#Comment_468599

I'll talk with one of our Mac developers and see if they have some ideas.

Martin Potter

https://community.logos.com/discussion/comment/468599#Comment_468599

Please note that my previous post did have my most current set of logs. I leave logging running because of intermittent issues.

Based on the contents of you uploaded archive, it appears that logging is not currently enabled; the Logos.log file is from January 24th and contains the entry "Logos Logging is not enabled". You can run the attached program to enable logging (restart is required if Logos is currently running) and archive your updated logs. If you experience any further high CPU usage after you have enabled logging and restarted, if you click on the "Sample" button, it will take a five second sample of the application and archive the sample results along with your current logs. This will provide more information so we can determine the cause of the CPU usage.

3531.LogosLoggingUtility.zip

Martin

https://community.logos.com/discussion/comment/469225#Comment_469225

You can run the attached program to enable logging

Is this utility available for general use? Seems to be an improvement over KS4J's AppleScript and Logos Log Scribe—even though both are excellent troubleshooting resources.

Martin Potter

https://community.logos.com/discussion/comment/469347#Comment_469347

Is this utility available for general use?

Yes, the application is available for use by anyone and will work with Logos 4 or Logos 5. If you encounter any error with the utility, please let me know.

KS4J's AppleScript and Logos Log Scribe—even though both are excellent troubleshooting resources

I completely agree, both of those applications have been excellent resources in assisting with troubleshooting. I made the new utility to overcome a couple of issues based on our specific internal use case along with simplifying the process of enabling and collecting logs to one application. The application is also signed, so it should run on Mountain Lion with the default Gatekeeper settings.

https://community.logos.com/discussion/comment/469370#Comment_469370

Yes, the application is available for use by anyone and will work with Logos 4 or Logos 5. If you encounter any error with the utility, please let me know.

Then, I will start recommending its use. What is the best URL for download?

Patrick S.

https://community.logos.com/discussion/comment/468557#Comment_468557

This is still a problem. Here are my logs and my most recent screen capture with the exceptionally high processor usage.8623.LogosLogs TIMOTHY HANKINS 20130304-115609.gz

This is absolutely not normal for any application on a Mac. Even for Logos, which is not an optimised Mac application, is not 64 bit, and which has to carry around baggage like Mono to run.

I also have a 27" iMac mid 2011. With more memory than you have but that should not be a major factor.

One tool you can use to more closely monitor Logos running (which will require going using the Terminal) and the resources it is using is to run the 'top' command in Terminal.

To do so:

In Activity Monitor find the 'PID' (process ID) of the Logos app, the column on the left. In your screenshot the Logos PID is 920.
Open a terminal window, Terminal can be found in Applications | Utilities
At the prompt (using the PID found in step one) type 'top -pid 920' (again 920 was the PID of Logos running in your screenshot, the PID will be different each time you run Logos)
You will see a display with lots of information (make terminal screen as wide as possible to see things). At the top is summary info for the whole system, below it you will see a table with many columns starting with PID then COMMAND which should show Logos.
Press 'q' on your keyboard to quit 'top' display

In normal usage (specifically with your system) with Logos just sitting, not doing anything you should see things like %CPU = 0.1, RSIZE = 295M, VSIZE = 1356M, STATE = sleeping (except when Logos 5 is 'phoning home').

This page http://docstore.mik.ua/orelly/unix3/mac/ch08_01.htm#sect1 has info on understanding output of top.

If I go into Logos and do a query like — Search All Text in Entire Library for "God" and then jump back to the terminal window I see the CPU usage jump up to ~ 100% it then goes down step by step back to 0.1 %CPU when all results are displayed. Then it also goes back into state sleeping. This is normal sort of system behaviour. If you are seeing significantly different then that is abnormal.

As to what is causing the high loads you are seeing that is something which needs to be investigated via looking at logs and so on.

the Rev

https://community.logos.com/discussion/comment/470335#Comment_470335

Patrick, I'm having the same problem. I have an iMac 27' guad core 16 gig ram. I've got around the problem by using an older layout. I have different layouts saved for different purposes. I started off using a much simpler layout, less resources open. That worked fine, no high CPU. Then I used an older layout which is as complex as what I've been currently using. Seems ok so far. I've also emailed Logos about this problem and they say they are looking into it. Perhaps this will help you keep working until they resolve this problem.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/469370#Comment_469370

Is this utility available for general use?

Yes, the application is available for use by anyone and will work with Logos 4 or Logos 5. If you encounter any error with the utility, please let me know.

KS4J's AppleScript and Logos Log Scribe—even though both are excellent troubleshooting resources

I completely agree, both of those applications have been excellent resources in assisting with troubleshooting. I made the new utility to overcome a couple of issues based on our specific internal use case along with simplifying the process of enabling and collecting logs to one application. The application is also signed, so it should run on Mountain Lion with the default Gatekeeper settings.

Thankful for Logos Logging application so updated references on a couple wiki pages => http://wiki.logos.com/Diagnostic_Logging#Mac and => http://wiki.logos.com/Mac_Troubleshooting

Keep Smiling [:)]

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/469434#Comment_469434

Yes, the application is available for use by anyone and will work with Logos 4 or Logos 5. If you encounter any error with the utility, please let me know.

Then, I will start recommending its use. What is the best URL for download?

Logos Support page => http://www.logos.com/support/logos5/mac/logging links to => http://www.logos.com/media/tech/LogosLogging.zip

Keep Smiling [:)]

https://community.logos.com/discussion/comment/470512#Comment_470512

Logos Support page => http://www.logos.com/support/logos5/mac/logging links to => http://www.logos.com/media/tech/LogosLogging.zip

Thanks, it looks good. Have added this link to my "Forum Links" file for future reference.

I am smiling, see [:D]

https://community.logos.com/discussion/comment/470545#Comment_470545

I am still having this problem. Here is a set of logs and a sampling from the tool posted previously. Specifically I took the sampling after I told Logos to close after the UI had gone but was left with the never ending "Synchronizing" window and the processors still running about 390% which they have been running at much of the day for me. Hope this helps! 1754.LogosLogs.a3w275.20130502-131906a.zip

7536.LogosLogs.a3w275.20130502-131919.zip

Rev. Fix

https://community.logos.com/discussion/comment/485576#Comment_485576

I'm having this issue as well. Anything that can be done about it?

the Rev

https://community.logos.com/discussion/comment/532894#Comment_532894

My work around is to stop using that layout. It is either corrupted or there are too many windows open. I've found that making a new layout or returning to a simpler one resolves this constant syncing.

Rev. Fix

https://community.logos.com/discussion/comment/532899#Comment_532899

Okay, Thanks!

https://community.logos.com/discussion/comment/533091#Comment_533091

https://community.logos.com/discussion/comment/534466#Comment_534466

Sorry Im having the same issue...

Logos.log

https://community.logos.com/discussion/comment/534467#Comment_534467

6014.Indexer.log

https://community.logos.com/discussion/comment/534467#Comment_534467

6014.Indexer.log

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/534475#Comment_534475

6014.Indexer.log

Looks like Library Index rebuild took 1 hour 24 minutes to complete, which is CPU intensive while resource files are being indexed.

Noticed log had some Bible Index errors; not know if bible index needs to be rebuilt. If want to manually rebuild, can use command:

rebuild bible index

Keep Smiling [:)]

Thomas Ball

https://community.logos.com/discussion/comment/534478#Comment_534478

6014.Indexer.log

Looks like Library Index rebuild took 1 hour 24 minutes to complete, which is CPU intensive while resource files are being indexed.

Noticed log had some Bible Index errors; not know if bible index needs to be rebuilt. If want to manually rebuild, can use command:

rebuild bible index

Keep Smiling

I'll ask Martin this week what "ERROR | 28 | ApplicationUtility | SQLite Error 28: multiple links to file" means. Can you paste the support info for the NRSV Aprocrypha?

DeWayne

https://community.logos.com/discussion/comment/534597#Comment_534597

This fix has worked for all my overheating and cpu issues.

Go into Logos 5 "preferences". Turn off Internet Access.

Once a month turn it on and you'll see the same amount of downloads that you'll see everyday if you leave it on. (avg 600+ MB) The updates are worse the MS Word. LOL well not as bad, but close enough. Why in the world do we want to have an update every day? Once a month is plenty unless something is broke.

If any Mac App downloads an update outside of the App Store, this is normal CPU and Overheating issues. I think also Logos 5 is calling home to much for system checks. I have yet to prove this. And I don't know why indexing has to happen all the time, once things are index that should be good until the next download. I've noticed indexing does not work as hard when the Internet is off. :-)

My Logos 5 now works great and to be honest I don't need an upgrade ever... In fact today I turned the Internet back on, first time in 3 months.

Lee

https://community.logos.com/discussion/comment/535061#Comment_535061

Something's broken. It's not designed to work this way.

Dave Hooton

https://community.logos.com/discussion/comment/535061#Comment_535061

Go into Logos 5 "preferences". Turn off Internet Access.

The most effective way to manage downloads & indexing is to set Automatically Download Updates to NO. You still have internet access for sync'ing your documents and resource metadata, but you can choose to download or not download an update when you receive a notification. If you wish software updates only then use the supplied link in the thread that advises a new version is available.

Patrick Fontaine

https://community.logos.com/discussion/comment/535146#Comment_535146

Im having the same problem

Dave Hooton

https://community.logos.com/discussion/comment/542809#Comment_542809

Im having the same problem

Please describe your problem - exactly what happens and also include logs as per http://wiki.logos.com/Diagnostic_Logging.

Are you on Mac or Windows? What is your computer? What version of Logos?

https://community.logos.com/discussion/comment/542857#Comment_542857

This problem persists. I have not been updating this thread mostly because of time constraints. However here are some log files including samplings that I have been collecting when the problem occurs, using the tool previously linked. I have thrown in a couple flagged as "good" to provide a contrast. The problem does seem to be directly related to synch though. I can't remember this ever coming up when the synchronization isn't running.

https://community.logos.com/discussion/comment/544503#Comment_544503

3122.LogosLogs.a3w275.20131014-155958.zip

0081.LogosLogs.a3w275.20130813-152529.zip

7002.LogosLogs.a3w275.20130521-155701.bad.zip

4666.LogosLogs.a3w275.20130516-151449.bad.zip

3108.LogosLogs.a3w275.20131024-102401.zip

https://community.logos.com/discussion/comment/544511#Comment_544511

6165.LogosLogs.a3w275.20130516-151850.good.zip

7608.LogosLogs.a3w275.20130516-111624.good.zip

Dave Hooton

https://community.logos.com/discussion/comment/544503#Comment_544503

I have not been updating this thread mostly because of time constraints. However here are some log files including samplings that I have been collecting when the problem occurs, using the tool previously linked. I have thrown in a couple flagged as "good" to provide a contrast.

The logs are inconclusive e.g. one of your "good" logs had sync errors whilst two "bad" ones did not! Frequency of syncing appears similar between "good" and "bad" logs. Also, none of the logs relate to the current Logos version 5.2 where Sync v1 is phased out.

Armin

https://community.logos.com/discussion/comment/544638#Comment_544638

The same issue is being reported in numerous threads. Here is another thread on the same issue:

http://community.logos.com/forums/t/68738.aspx?PageIndex=1

I hope that the logs will eventually help Logos track down the problem as it is pretty annoying.

Armin

https://community.logos.com/discussion/comment/544638#Comment_544638

Sorry to be so unhelpful with the previous logs. I was actually unable to load up the logs I took on the 20th because I received an error from the website while unloading. I had assumed that for some reason the files were corrupt. But I am having the same error today while trying to upload the log files I have just taken. So apparently I no longer can post logs online towards resolving this problem.

I will say that my previous assumption about the sync must have been incorrect though because logos is taking 150%-250% of the processor and the sync is not running.

I wonder if having upgraded to Mavericks is contributing to the problem.