<Error>: CGContextGetCTM messages

[Sara Burke]

Roger, that post to the Oracle forums is indeed the same issue.

Yes, this happens to me with the following Java versions:

Java SE 6 1.6.0_29 (Apple)
Java SE 6 1.6.0_31 (Apple)
Java SE 7 1.7.0_04 (Oracle)
OpenJDK 7 binary from Oracle

>From this I suppose we can conclude this isn't necessarily related to OpenJDK 7, so I won't prolong this on the mailing list :) Thanks everyone!

-S



On Jun 26, 2012, at 2:27 PM, Roger Lewis wrote:

Hi Sara,

There is also a posting on the Oracle Forums indicating that the problem is happening on Apples Java as well. No release version is mentioned, though it was posted on June 7th. 10.7.4 was released on, or about, May 9th.  At that point the 6u31 seems to be the most current release.
https://forums.oracle.com/forums/thread.jspa?threadID=2399029

The likely configuration there is 10.7.4 with 6u31, but just a guess.

6u31 notes (last updated April 13th)
https://support.apple.com/kb/HT5242

-Roger


On 6/26/12 10:40 AM, Sara Burke wrote:
Hi all,

I am new on this list, so I do apologize for any format issues.

I came across a post to this mailing list of which I am having the same issue so I was wondering if anyone has heard of any root causes and/or workarounds:
http://mail.openjdk.java.net/pipermail/macosx-port-dev/2012-June/004407.html

More details:

My application emits the following messages; for easier reading, MY_APP replaces the actual application name:

Jun  1 14:49:12 sburke-maci MY_APP[5611]<Error>: CGContextGetCTM: invalid context 0x0
Jun  1 14:49:12 sburke-maci MY_APP[5611]<Error>: CGContextSetBaseCTM: invalid context 0x0
Jun  1 14:49:12 sburke-maci MY_APP[5611]<Error>: CGContextGetCTM: invalid context 0x0
Jun  1 14:49:12 sburke-maci MY_APP[5611]<Error>: CGContextSetBaseCTM: invalid context 0x0

Same messages with my sample Java application.

This did not happen in Mac OS X versions prior to 10.7.4. I confirmed that this still occurs in the latest developer preview of Mountain Lion and the latest Java SE 7, including OpenJDK 7.
Regardless of whether or not this is a Java-related issue, the fact that these messages suddenly appeared with 10.7.4 insinuates that there is an OS bug somewhere or perhaps someone left in some debugging print statements.
Posting this topic here to see if anyone else has come across this issue and/or knows of a workaround.

Thanks,
Sara



-----------------------------------------------------------------
 Sara M. Burke
 Ext. 7476






-----------------------------------------------------------------
 Sara M. Burke
 Ext. 7476