URGENT: Log reading skills needed (dev, KS4J...)

For a long while now I've gotten endless error massages in my console log. Since they included my internet provider's name, I ignorantly assumed they had to do with the connection. Now I just figured out what they are: they start the second I move over to Logos, and end the second I leave Logos! Or, more exactly, the second I move to or from the Space Logos is in.

They also seem to keep Finder at around 100% CPU, which isn't good. I'm hoping that if I could get rid of these, some of my performance issues might go away as well. I was about to start a number of threads, but now I want this fixed first, to see what difference it makes, if any.

So what can you log gurus make of this:

<time> com.apple.Dock.agent[125] <time> <my IP and internet provider> Dock[125] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]
<time> com.apple.Dock.agent[125] <time> <my IP and internet provider> Dock[125] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformsAtPlacement: Singular matrix at index 0: [nan 0.000 0.000 nan]

You can also find some slightly similar log lines posted in http://community.logos.com/forums/p/71788/499945.aspx#499945, except those were in the logos.log.

Find more posts tagged with

Comments

fgh

Bump.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/500620#Comment_500620

I've asked a Mac developer to investigate this issue.

Mark Barnes

Some googling suggests that Logos is probably trying to draw an invalid window, possibly one with no dimensions.You might be able to verify this with Quartz Debug.

fgh

https://community.logos.com/discussion/comment/500637#Comment_500637

Thanks.

I also found an interesting chart some hours ago that I didn't know I had:

See that huge drop at the end of the first one? That's when I clicked to install RC3. Now, it seems logical for the blue (User) to drop when Logos is shut down, but why does the red (System) drop so much? Why does Finder go from an almost constant 100% while Logos is open, to almost zero as soon as it is closed? I think the fans have run more today than they normally do in a month.

Though I no longer believe the high CPU is directly related to those log lines. That seems to be a separate issue. The log errors only occur when I'm in Logos Space, the high CPU occurs virtually the whole time Logos is open. Plus the log errors have been there a very long time, while the CPU issue seems new.

fgh

https://community.logos.com/discussion/comment/500654#Comment_500654

Sorry, Mark, no idea what you're saying. You're far beyond my computer skills.[:)] Or were you talking to Bradley?

Mark Barnes

https://community.logos.com/discussion/comment/500656#Comment_500656

I was talking to anyone who was listening [:)]. I'm not a Mac person, so I can't really help, however. But given that the problem occurs when you open/close Logos I wondered whether there was a problem painting the "Synchronizing" pop-up that appears at open/close. If so, that's a problem that Logos will need to fix, but my Mac knowledge is way too inadequate to know whether that's actually the case.

fgh

https://community.logos.com/discussion/comment/500666#Comment_500666

given that the problem occurs when you open/close Logos

The CPU problem seems to start when I open Logos, but those lines in the log only occur while I'm in the 'Space' where Logos is already open, not when Logos is open in the background.

Mark Barnes

https://community.logos.com/discussion/comment/500670#Comment_500670

The CPU problem seems to start when I open Logos, but those lines in the log only occur while I'm in the 'Space' where Logos is already open, not when Logos is open in the background.

I'd misread your initial post, and though it was on starting/closing Logos, so it's not the synchronising pop-up. But similar problems with other apps, particularly with Chrome, are also triggered by Spaces, and, as I said, suggest some kind of invalid window is being painted.

fgh

https://community.logos.com/discussion/comment/500672#Comment_500672

similar problems with other apps, particularly with Chrome, are also triggered by Spaces

Yes, 'Chrome' and 'Spaces' were the two understandable words I found when I initially tried to google it. Not much, but it was what made me figure out that the lines occurred when I was in Logos' Space.

fgh

https://community.logos.com/discussion/comment/500670#Comment_500670

This CPU issue is one weird bug. Before reporting it, I made sure to close all programs one by one, as well as start them one by one, and at that time most things pointed to Logos. In the following days I had doubts, but there were always also new things happening that clearly pointed to Logos.

Then yesterday I suddenly realized that the CPU had been normal since the day before -- and Logos had been open the whole time (as had every other program I normally use). I also realized at the same time that another issue was gone as well -- and that one I knew to be caused by iStat Menus, which I also remembered having updated at least once, quite possibly twice, recently. So Logos acquitted, iStat guilty... Except that after digging through a lot of logs it turns out that it was only updated once, and that was between my earlier posts here. And no other program was updated on the relevant days either.

So, no explanation, but the issue was gone, the computer was a nice 58° instead of an awful 82°, and I went here and wrote up a paragraph about how Logos was innocent after all. Only while writing that I restarted Logos to get logs for another thread -- and immediately the CPU skyrockets again. I wait a while, hoping it will go down again after the initial caching and whatever else it does after startup is finished, and it does.

Unfortunately, it doesn't last. I make one search as a test, and immediately Finder goes back up to 100%, and this time it stays there until I shut down the computer for the night, although I don't use Logos again.

And then today everything is fine again[:^)]:

My latest theory is that it may have to do with whether I start Logos before or after other programs, but I will need a couple of days to test that, so if anyone has any better ideas...

And I'd still like to get the log issue solved as well.

fgh

https://community.logos.com/discussion/comment/501937#Comment_501937

This CPU issue was gone for about a week. I never managed to figure out how/why it starts, or how/why it stops, but it was gone, and I was beginning to believe it was gone for good. Then I download SR1, and the moment I hit Install, it was back:

There is no way this isn't Logos related. But once it appears, it remains, no matter how many programs I shut off. It's like the install turned over a switch somewhere deep on the system level.

It took me five or six restarts, including, finally, a shift-start, to get back to normal again. But the thing is, I've tried a shift-start at least once before over the course of this thread, and that time it didn't help. So that's not a reliable solution either.

And I'm still waiting for that Mac developer to get back to me...

Bradley Grainger (Logos)

<time> com.apple.Dock.agent[125] <time> <my IP and internet provider> Dock[125] <Error>: kCGErrorIllegalArgument: CGSSetWindowTransformAtPlacement: Singular matrix [nan 0.000 0.000 nan]

One cause of this problem was fixed in 5.1 SR-1. (There are no known other causes.)

Are you still seeing error messages like this after upgrading to 5.1 SR-1, or are they fixed.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/505896#Comment_505896

There is no way this isn't Logos related.

Logos 5.1 doesn't use any Finder API calls, so we're not aware of any mechanism by which this could be triggered by Logos.

fgh

https://community.logos.com/discussion/comment/506127#Comment_506127

One cause of this problem was fixed in 5.1 SR-1. (There are no known other causes.)

Are you still seeing error messages like this after upgrading to 5.1 SR-1, or are they fixed.

You're correct. The last lines seem to be from the 11th, which was probably when I installed SR 1.

There is no way this isn't Logos related.

Logos 5.1 doesn't use any Finder API calls, so we're not aware of any mechanism by which this could be triggered by Logos.

But how can it start the very second I install a Logos update, if it's not Logos related?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/507408#Comment_507408

But how can it start the very second I install a Logos update, if it's not Logos related?

I don't know, sorry.

But I do know that there are an awful lot of threads found on the Internet when googling for "finder high cpu usage 10.6". A common thing that seems to be posted on those threads is that this can be caused by having "Calculate Folder Size" checked in Finder View Options; is that checked on your system? If not, maybe some of the other suggestions in those threads may be helpful. Sorry I don't have a more specific, helpful answer.