High CPU Usage
Lately I've been having an issue with Logos 4 and CPU usage... when I launch the application the CPU (in the activity monitor) pegs at 100%, this to me is expected... however... it remains at or near 100% CPU usage for 10+ minutes fairly consistently. This is without loading anything up. But it also does it after I have loaded a layout... the layout finishes loading... then it sits for 10+ minutes at 100% CPU usage and then finally drops drastically to 1-4% usage and is now ready to use.
Now... unless I am mistaken.. the indexer is not running. When the indexer runs, say after a new version of the software... it pops up in my menu that it's indexing, gives me the remaining time ect...
The activity monitor says that it's "Logos Bible Software 4" that is using the CPU at 100%.
I have 8gb RAM in the machine and am running OS 10.6.7.
I don't remember it doing this until recently... maybe the last month or so. Any idea's?
Comments
-
When you are initially opening the program, what is loading? A blank layout, the homepage?
Is it the same layout you are using that causes this or does the high CPU usage occur after loading any named layout?
We recently had another user with a similar issue which was resolved when he rebuilt the layout in question. So, you may want to try that.
Diagnostic logging by default will be removed in 4.3, but if you have the stable release (4.2b, at present) your program should already be logging. If you could recreate the behavior and post your logs that would be helpful. You can find some instructions and useful information for doing so here: http://wiki.logos.com/Mac_Troubleshooting#How_to_Report_Bugs_in_Logos_4_Mac
0 -
Tonya J Ross said:
Diagnostic logging by default will be removed in 4.3
That's sad to hear. Please give us the choice to enable it in Preferences, if you haven't already.
Mac Pro (late 2013) OS 12.6.2
0 -
Hi fgh
fgh said:That's sad to hear. Please give us the choice to enable it in Preferences, if you haven't already.
From the release notes for 4.3 Beta 5
Diagnostic Logging
- Full Logging has been disabled to improve performance in the program. Logging can be enabled temporarily or permanently by following the steps below:
- Temporary logging: Open Logos 4 by pressing the Command key immediately after clicking the icon in the Dock, keeping Cmd held down until the Sign In window appears. Click the Sign In button to open the program with logging enabled for that session.
- Permanent logging: Quit Logos 4 and open the Terminal utility. Enter defaults write com.logos.Logos_Bible_Software_4 LoggingEnabled -bool YES.
- Disable Permanent logging: Quit Logos 4 and open the Terminal utility. Enter defaults write com.logos.Logos_Bible_Software_4 LoggingEnabled -bool NO.
- Crash logs will still be generated with logging disabled; however, if a crash occurs, development will need the Logos4.log or Indexer.log as well.
Graham
0 - Full Logging has been disabled to improve performance in the program. Logging can be enabled temporarily or permanently by following the steps below:
-
I'm hardly the only Mac user who's never used Terminal and is hesitant to do so. Besides, we shouldn't have to open another program to do this. It should be in Logos Preferences. And to tell us that logging has been disabled but if there's a crash they need the logs, that, frankly, sounds pretty stupid to me. If they disable the logging they ain't gonna get any logs.
Mac Pro (late 2013) OS 12.6.2
0 -
I agree with fgh. We really shouldn't have to go into Terminal to change preferences. I've opened Terminal just once recently. I realize this puts more work on the L4M dev guys, but the average Logos user probably would rather not be tinkering in a place that could wreak havoc.
The mind of man is the mill of God, not to grind chaff, but wheat. Thomas Manton | Study hard, for the well is deep, and our brains are shallow. Richard Baxter
0 -
Tonya J Ross said:
Diagnostic logging by default will be removed in 4.3
Hmmm - interesting. Seems like part of the ongoing hunt for performance. Actually I would support not having logging running all the time. Constant logging in a program can add unwelcome performance degradation.
However as someone fully comfortable with the terminal I would still say that it is not 'friendly' of the application to make people, already stressed because their high cost application is constantly crashing, have to go to the Mac terminal and type some obscure command. The Mac terminal is for hackers, most Mac users won't even know a command prompt exists in Mac OS X. I can just see the forum posting now from a Rev. or Prof. of Biblical Languages X writing "you want me to do what?!?"
If the developers can't incorporate it in the UI at this time (pressured looking for ways to increase performance?) then make something a simple and clickable like an AppleScript utility to turn it on and off and include it with the Logos 4 application.
Also, as fgh says, how can users add a crash log, after the fact, when crash logging is turned off by default? But I'm splitting hairs here, obviously if a user like Chuck here has a serious and recurring issue then the logging can be turned on and the log saved.
So - on the whole I think it is good idea to not have logging on by default but please make it more user friendly and polished for users to turn on and get logs. What would be very nice is to have a log posting facility built into Logos 4 like a button...
'Click here to have logs forwarded to Logos support'
Gets emailed using user's Logos logged in account details.
"I want to know all God's thoughts; the rest are just details." - Albert Einstein
0 -
Graham Criddle said:
From the release notes for 4.3 Beta 5
Diagnostic Logging
- Full Logging has been disabled to improve performance in the program. Logging can be enabled temporarily or permanently by following the steps below:
- Temporary logging: Open Logos 4 by pressing the Command key immediately after clicking the icon in the Dock, keeping Cmd held down until the Sign In window appears. Click the Sign In button to open the program with logging enabled for that session.
- Permanent logging: Quit Logos 4 and open the Terminal utility. Enter defaults write com.logos.Logos_Bible_Software_4 LoggingEnabled -bool YES.
- Disable Permanent logging: Quit Logos 4 and open the Terminal utility. Enter defaults write com.logos.Logos_Bible_Software_4 LoggingEnabled -bool NO.
- Crash logs will still be generated with logging disabled; however, if a crash occurs, development will need the Logos4.log or Indexer.log as well.
Incorporated into wiki http://wiki.logos.com/Diagnostic_Logging page (with copy and paste commands for terminal use), currently linked from Mac Troubleshooting => How to Report Bugs in Logos 4 Mac
fgh said:Tonya J Ross said:Diagnostic logging by default will be removed in 4.3
That's sad to hear. Please give us the choice to enable it in Preferences, if you haven't already.
Both sad and glad; for many Logos users, changing default should improve Logos 4 Mac performance (anticipating noticeably faster on older hardware).
Concur with Logos 4 Preference request, which would benefit Logos 4 Mac and PC users (e.g. Enabling Logging discussion)
Keep Smiling [:)]
0 - Full Logging has been disabled to improve performance in the program. Logging can be enabled temporarily or permanently by following the steps below:
-
fgh said:
And to tell us that logging has been disabled but if there's a crash they need the logs
I believe L4M will still generate a Crash Log in that event. However, that will not contain all the information of a full logging file.
0 -
Patrick S. said:
If the developers can't incorporate it in the UI at this time (pressured looking for ways to increase performance?) then make something a simple and clickable like an AppleScript utility to turn it on and off and include it with the Logos 4 application.
Good suggestion [Y]
0 -
Patrick S. said:
Seems like part of the ongoing hunt for performance. Actually I would support not having logging running all the time. Constant logging in a program can add unwelcome performance degradation.
That's fine if you don't encounter any bugs, don't bother to report any bugs, or find speed your biggest issue, but to me the speed issues are far behind the dozens or hundreds of bugs I encounter pretty much every time I open this program. And if I don't attach logs, the bug report is going to end up last in the queue (that is if they even put it in the queue). In my opinion they should get rid of at least 90% of known bugs before they disable default logging, but if not, they should at least make it easy for those of us who want to keep it.
Patrick S. said:However as someone fully comfortable with the terminal I would still say that it is not 'friendly' of the application to make people, already stressed because their high cost application is constantly crashing, have to go to the Mac terminal and type some obscure command. The Mac terminal is for hackers, most Mac users won't even know a command prompt exists in Mac OS X. I can just see the forum posting now from a Rev. or Prof. of Biblical Languages X writing "you want me to do what?!?"
Exactly.
Patrick S. said:Also, as fgh says, how can users add a crash log, after the fact, when crash logging is turned off by default? But I'm splitting hairs here, obviously if a user like Chuck here has a serious and recurring issue then the logging can be turned on and the log saved.
If you read the release note quote again you will find that crash logging will still be on, but lots of the time the developers need the other log[s ] as well. And if the bug isn't a crash they definitely need them. Also, lots of the time bugs aren't [immediately] repeatable, or you don't have hours to spend trying to hunt down the exact cause of them. You just take a quick screen shot, zip the current log and get on with whatever you're doing, and then you write up a quick post about it later, perhaps adding new details and logs the next time it happens. But to do that you need to have logging on at all times, otherwise there won't be anything for the developers to work with, so they won't.
Patrick S. said:What would be very nice is to have a log posting facility built into Logos 4 like a button...
Have you tried the Logos Log Scribe? (I haven't, but it's supposed to be good).
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:Patrick S. said:
What would be very nice is to have a log posting facility built into Logos 4 like a button...
Have you tried the Logos Log Scribe? (I haven't, but it's supposed to be good).
I use LogosLogScribe regularly, but it only collects logs and does not turn logging on.
0 -
I've submitted a request for an auto script to enable logging in the Mac version if possible, like the EnableLogging.js script that is available for the Windows version.
0 -
Thanks.
Mac Pro (late 2013) OS 12.6.2
0 -
Jack Caviness said:Patrick S. said:
If the developers can't incorporate it in the UI at this time (pressured looking for ways to increase performance?) then make something a simple and clickable like an AppleScript utility to turn it on and off and include it with the Logos 4 application.
Good suggestion
AppleScript application posted => http://community.logos.com/forums/p/33530/253083.aspx#253083
Keep Smiling [:)]
0
