15 replies to this topic

[William Cross]

Mac OS 10.4.9
Accordance 7.2

Console Log is spitting out endless messages only when the Instant Details window is open. Should this be happening? It stops the minute I close the window.

Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext....

[Joe Weaks]

William,
The problem is clearly with the attempt to draw the text in the instant details box using Quickdraw.

"To simplify debugging, attempts to call QuickDraw to do any drawing between calls to QDBeginCGContext and QDEndCGContext are now logged to the console as "Ignoring QuickDraw drawing between QDBeginCGContext and QDEndCGContext". (r. 2802466)."
-- Apple Technical note 2053

This indicates to me that the likely candidate is a conflict with something else you have running that uses Quickdraw, possibly a poorly implemented Quicktime plugin. Do you have any Macromedia or Adobe apps running?

A way to test would be to restart, after having disabled any graphic related items for the Startup Login items in sys preferences.

Then launch Accordance and console.app to see if you still get the error. If not, then you can add apps and find the culprit.

You didn't say whether the ID box is actually working (ie. showing the info).

[William Cross]

Yes the Instant Details window is working.
I went back and rebooted in Safe Boot mode with everything turned off and started up Accordance. Then I opened up the Console Log.
When ever I move the mouse over text and the Instant Details window registers the tagging for each word it the Console window pops to the front with that same message over and over. So I have no idea. I had no extra programs or things running and it still did it.

Any ideas. Is this normal? Or is it just my computer?

[William Cross]

I created a new user and tried running Accordance in that new account but still had the same problem.

Now I am back in my original and only user account.
I tried trashing the Preferences, but no avail.
I went back into the Console Log and I noticed when I start up Accordance I get this:

May 18 12:32:11 William-Cross-Computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: FOExceptionMainHandler caught a fatal exception at 0x000bda68\n
May 18 12:20:45 William-Cross-Computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: ATSServer got a fatal exception! Please check /var/log/ats.log, also viewable in Console.app

Then this starts appearing endlessly whenever I move the mouse:
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext

I checked the var/log/ats.log and see this appearing over and over but with a different number at the end each time:
ATSServer got a fatal error (status: -6) while processing a message (id: 26) from pid=247.

Any Ideas?

Edited by William Cross, 18 May 2007 - 01:34 PM.

[Mike Garrity]

'Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext'

Accordance has been responsible for this message before. I consider it a message for the developer of the application that the code is mixing calls to Apple's graphic toolboxes. We have cleaned up previous occurances of this message. I don't think this is a performance issue, but we try to clean up the code when we can reproduce these messages.
I have not been able to reproduce these messages. (more on that later...)

I went back into the Console Log and I noticed when I start up Accordance I get this:

May 18 12:32:11 William-Cross-Computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: FOExceptionMainHandler caught a fatal exception at 0x000bda68\n
May 18 12:20:45 William-Cross-Computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: ATSServer got a fatal exception! Please check /var/log/ats.log, also viewable in Console.app

Then this starts appearing endlessly whenever I move the mouse:
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext

I checked the var/log/ats.log and see this appearing over and over but with a different number at the end each time:
ATSServer got a fatal error (status: -6) while processing a message (id: 26) from pid=247.

Any Ideas?

ATSServer is Apple Type Solutions Server and is used for system-wide font management.

I wonder if you have a corrupt font and need to run the font fixer to possibly fix Accordance fonts...

There is a chance this has something to do with the previous error, maybe?


Let us know what happens...

Mike

[William Cross]

I ran the latest Font Fixer Utility and checked for any fonts that registered conflicts or would not validate.
Came up with nothing. After that I restarted and then started up Accordance. The same error in the Console Log keeps coming up.

May 18 13:18:58 William-Cross-Computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: FOExceptionMainHandler caught a fatal exception at 0x000bda68\n
May 18 13:18:58 William-Cross-Computer /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framework/Support/ATSServer: ATSServer got a fatal exception! Please check /var/log/ats.log, also viewable in Console.app
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext


One new thing I noticed, while Accordance is open if I click on a Finder window and move it or change to a different folder the Console Log registers:
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext

But if I close Accordance it stops. It SEEMS that Accordance is causing some kind of conflict.

I also tried deleting the ATS.plist file and restarting, but to no avail.

Edited by William Cross, 18 May 2007 - 04:24 PM.

[William Cross]

After much Font fixing and fussing the ATS error messages seem to have stopped.
Now it is just back to the original deal.


Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext
Ignoring Quickdraw drawing between QDBeginCGContext and QDEndCGContext...


Of course I can stop this by just turning off the Instant Details Window, but that would spoil one of the programs best features.

[jpkang]

A couple of suggestions/questions:

Have you tried cleaning caches, repairing permissions, and rebooting? (You may well have, but you didn't explicitly allude to these steps above)

Did the messages start just after updating to 10.4.9? If so, it might be worth reinstalling with the 10.4.9 combo (not delta) updater.

ATSServer got a fatal error (status: -6) while processing a message (id: 26) from pid=247.

Did you note which process had ID 247?

Unlikely given your Safe Boot experience, but is it possible that you're running some kind of interface customizing software (e.g., ShapeShifter, ThemePark, many Unsanity Haxies) for OS X that is intercepting calls?

In the meantime, why not turn off Console.app's preference to bring the log window to the front on updates to aid productivity, since it appears to have a negligible impact on performance?

Hope something here helps...

[Mike Garrity]

Another quick question/verification...

Are you sure you are running version 7.2 of Accordance?

If you check 'About Accordance...' then you can verify you are running 7.2.
{Helen commented to me that sometimes the installers/updaters leave the icon in the dock that points to your previous version of Accordance
AND these messages were cleaned up in a previous version}

If you verify that it is 7.2 and try JP's suggestions then if you could post a screen shot of your Accordance session then maybe it could
help us recreate the console log messages.

Mike

[William Cross]

Thank you for your suggestions.

Here is what I have just done.

Reinstalled the Accordance 7.2 Updater
Ran the OS X 10.4.9 Combo Updater, not the delta.
Cleaned the Font cache.
Started up in Safe Boot mode.
Opened Console.
Opened Accordance.
Opened About This Mac.
Opened Grab.
Took a timed screen capture.
Clicked Accordance to bring the front.

Attached is my screen grab.

[jpkang]

What are you using to customize the appearance of the Trash?

And I would suggest clearing all caches (including possibly kernel extensions cache; I don't believe these are cleared even by a combo updater) since there could be an otherwise unexpected interaction between Accordance's calls and something else that is trapping for them that is persisting between reboots. There are many, many utilities that can simplify this process.

[William Cross]

Nothing is running to actively change the Trash Can.
I had used CandyBar to switch out some Icons.

I will try you suggestions clearing out the caches and try running Applejack.

Thank you

[William Cross]

I ran Applejack in Deep Auto mode, which cleans out all of the caches, but the problem still persists.

"Deep Auto mode: If you want to let AppleJack clean out all cache files, including the Launch Services database and any cached User Pictures, use 'applejack AUTO' instead. Use this if you still have problems booting after running AppleJack already."

[Mike Garrity]

Sorry to take so long to reply.

Your screen shot really helped identify the problem area!
The debug message appears when there are details about a text with Strong's Numbers.
(I was testing with GNT-T not GNT-TRS for example)

We should be able to fix this in the next bug release.

Mike

P.S. How many words is a screen shot worth?

[William Cross]

That is great!
I also loaded up a non Strongs number text and the message went away.

Thanks and I look forward to that fix!

[Joe Weaks]

William,
Do note what JP suggested... turn off automatic notification in Console.app. The error is not a critical one, so it's best to ignore it.