BUG: "App is now idle" -- but CPU still above 100% (and program wouldn't quit)

I woke up the computer at 13.55 Swedish time. Some minutes later it dawned on me that the CPU was sky high. Checking Activity Monitor, I found that Logos was using more than 100%, although I hadn't touched it today. Went over to Logos, but didn't see anything going on. Closed a tab. Opened the log, but didn't see anything I could understand (plenty of errors and warnings, though, both today and yesterday, and for many different things).

At 14.07 the log wrote "App is now idle", but Activity Monitor still showed

At 14.10 I updated the layout and told Logos to quit.

Some time after 14.20 I realized it still hadn't. Checking the log I found a "now idle" at 14.15, and a "no longer idle" at 14.20. I gave up and clicked the Exit Now button at 14.26.

At 14.35 I gave up again and force quit.

All through this the CPU was above at least 90%.

Several people in this thread seem to have similar problems: CPU usage bug?. And I myself has had lots of high CPU usage, constant beach balls, almost daily force quits, and plenty of crashes, since upgrading to L5.

(And in the middle of writing this I managed to accidentally click the Logos icon instead of the Log icon, thus destroying the log. That's when you're very happy for Time Machine! The TM log stops at 14.28, but most of it is there. Looking at it, I'd prefer not to upload it here, though, so please advise what e-mail address you want me to send it to.)

Find more posts tagged with

Comments

Mike

I checked with one of our developers to make sure I understand this correctly. The short version being, without a log of the instance, we can only guess at what might have been going on. If you can provide that log, this may be helpful.

Personally, I tend to avoid "sleeping" my computer (Windows) as it inevitably introduces extra variables that could potentially lead to problems in any application. I don't know if Macs really handle this better, but that's my personal preference, to avoid it.

As for what was reported from your logs, "Application Idle" refers to whether the user is actively interacting with the application. It does not represent whether Logos is working or not. The logs track user interaction and key information that is helpful when troubleshooting. If we logged every line of code we execute, we'd spend too much time writing to the log and very little would get accomplished in the application.

This being the case, it is possible that Logos was processing some large amount of data in the background when it awoke. Perhaps we had some searches running or visual filters that were loading back into memory, something like that. I don't have data to really know for sure what it was exactly doing at the time.

We've added some additional steps at www.logos.com/support/logos5/mac/logging which might help us capture more data if you can reproduce this problem. "Step 4" includes instructions for "Sampling" the process, which might be helpful in conjunction with the new logs.

fgh

https://community.logos.com/discussion/comment/468542#Comment_468542

If you can provide that log, this may be helpful.

I can, if you give me the e-mail address I asked for.[;)]

it is possible that Logos was processing some large amount of data in the background when it awoke. Perhaps we had some searches running or visual filters that were loading back into memory, something like that.

That's what I checked for but didn't see. But I can send you a screenshot of the layout with the e-mail.

Mike

https://community.logos.com/discussion/comment/468554#Comment_468554

support@logos.com will work. Please reference this thread in your email.

Jack Caviness

https://community.logos.com/discussion/comment/468542#Comment_468542

Personally, I tend to avoid "sleeping" my computer (Windows) as it inevitably introduces extra variables that could potentially lead to problems in any application. I don't know if Macs really handle this better, but that's my personal preference, to avoid it.

Have disabled sleep on Macs for the last several years as the nap seemed to negatively affect some applications. This was before I began using Logos extensively, so cannot testify as to sleep's effect there.

fgh

https://community.logos.com/discussion/comment/468542#Comment_468542

I just sent logs and layout details in an e-mail with your name on the subject line.

I also did some further testing. I closed the layout, waited for the CPU to go down, and then reloaded it. It only took about a minute to fully load, with the CPU back to normal. And that was from a closed layout. In the OP, the layout was already fully loaded, only the computer had slept a while. And I hadn't even tried to access Logos yet. So there certainly isn't anything in the layout explaining that kind of CPU usage for that length of time.

I used to shut off the computer every night. In fact, until I went from 2 to 8GB of RAM in November-December I usually had to restart 2-3 times a day. But since then I've become lazy and only do it every 2-3 days. All other Mac users seem to leave their computers on for weeks at an end, never restarting except when some update forces them to, so that certainly shouldn't be a problem.

Thanks for teaching me about the logs. All I know about such is what I've had to pick up here.[:)] So that explains the first "now idle" line. However, I feel pretty confident there shouldn't be another "now idle" line in the log five minutes after I've told the program to quit. By that time it should be already closed. And I also believe that the "no longer idle" line another five minutes later happened 1-3 minutes before I went back to check why it hadn't shut down yet.

Mike

https://community.logos.com/discussion/comment/468609#Comment_468609

I've noticed that not needing to reboot is a common opinion among Mac users, with reference to better RAM management than Windows. This is also common among Linux users which I understand handles RAM the same as OS X. However, I've since learned a little bit about OS X's "Shared Memory" which is apparently somewhat limited compared to other OS and prone to clogging up if applications do not exit correctly or crash (not just Logos), so I'm still a reboot advocate for Mac.

That said, I received your log and we'll look it over. Meanwhile, if you can send me a "Sample Process" while the apparent hang is occurring, this would be incredibly useful for Development.

Logos should be creating a Logos.map file to go with it, which is necessary to read the sample correctly. We'll need a copy of the sample, the Logos.map and the Logos.log to get the full picture. I'll respond to your previous log so you have an email address to reply directly from.

fgh

https://community.logos.com/discussion/comment/468630#Comment_468630

Meanwhile, if you can send me a "Sample Process" while the apparent hang is occurring, this would be incredibly useful for Development.

Yeah, well, I haven't seen this particular scenario before, and have no idea if I'll see it again, so that might not be so very easy... [;)]

But I can certainly do it during one of my regular beach ball > force quits. No guarantee that's the same issue, though.

Please look at all of yesterdays errors and warnings while you're at it, in case that gives you any hints about my horrible performance generally.

fgh

https://community.logos.com/discussion/comment/468640#Comment_468640

Mike, could you take a look at Force quit on mac every time? If this does indeed have to do with leaving the Mac on overnight, that may be your best chance to get samples.