04-09-2014, 02:28 PM | #11 |
Senior Member
Join Date: Apr 2011
Posts: 280
|
|
04-10-2014, 09:11 AM | #12 |
Senior Member
Join Date: Apr 2011
Posts: 280
|
Hi Logan, please check your private messages, there are further instructions that could help in fixing your issue. Thanks
|
04-30-2014, 01:30 PM | #13 |
Member
Join Date: Oct 2011
Posts: 52
|
Christian, would it be possible to post a quick fix update to the 2.2 beta to prevent the gigantic amount of console logging of messages - it's the only thing holding me back from using it:
WindowServer(152): _CGXGLDisplayContextForDisplayDevice: No matching context for device )0x7fa6c0608d70) - disabling OpenGL |
05-01-2014, 08:46 AM | #14 | |
Mac Team
Join Date: Feb 2009
Posts: 606
|
Quote:
We're looking at this now. These are WindowServer logs and not directly in our control but we're trying to see if we can do anything else than raising a bug with Apple. The Window Server should not continuously try to use an unsupported OpenGL function and be surprised about the outcome every 250 milliseconds. The system logger is clever though and does not log streams of identical log lines when they're too frequent. Cheers, Carlo |
|
05-06-2014, 12:14 PM | #15 |
Mac Team
Join Date: Feb 2009
Posts: 606
|
Hi Mick,
We have not found a way to work around the excessive Window Server logging while using the API recommended by Apple for Mavericks. Googling around it looks like other solutions are affected as well. We opened a bug with Apple. Cheers, Carlo |
05-07-2014, 05:33 PM | #16 |
Junior Member
Join Date: Jan 2013
Posts: 6
|
Any update? It has been over a month....and many of us have more than one monitor connected to our Mac's...thus the need for this product.
|
|
|