|
|
Thread Tools | Search this Thread | Display Modes |
05-15-2014, 08:54 PM | #11 |
Member
Join Date: Oct 2011
Posts: 52
|
I got a reply from the Notebook developer, and he found something interesting that I hope gives a clue to the DisplayLink developers:
Hi Mick, NoteBook does not use OpenGL directly. OS X might be invoking it on NoteBook's behalf, but for what reason I have no idea. I don't know much about OpenGL or DisplayLink. I Googled _CGXGLDisplayContextForDisplayDevice to see if I could find any info to help you track it down. I ran across your post of this message, so you've read everything they had to say there. Here is the only other result that I thought might have some good info. It was talking about old drivers (kexts) of some sort. Search for _CGXGLDisplayContextForDisplayDevice to see the comment: http://forums.macrumors.com/archive/...93194-p-4.html |
05-16-2014, 05:15 PM | #12 |
Member
Join Date: Oct 2011
Posts: 52
|
So while things are better after zapping the PRAM, I've decided the console logging is still just way too crazy with normal use, so it's back to 2.1 for me. I'll keep (im)patiently waiting for the next beta. I know DisplayLink are implicating at Apple, but version 2.1 didn't log anything like this vast amount of stuff to the console.
|
07-09-2014, 12:59 PM | #13 |
Member
Join Date: Aug 2012
Posts: 36
|
Hmm, I'm on the 2.2 version of the driver (not the beta) on 10.9.4 and it's still spewing out these messages in Console.app. Two colleagues have exactly the same issue, one is on a MBA mid 2013, the other is on a 13" MBP (I believe 2012), my MBA is a mid 2012. We're all on 10.9.4.
I'll try zapping the PRAM. I've been waiting to use DisplayLink DL3xxx for more than a year since support was available and since then it's been a lot of issue's. This is another annoying one... |
07-09-2014, 02:18 PM | #14 |
Member
Join Date: Aug 2012
Posts: 36
|
After zapping PRAM and resetting SMC on 10.9.4 with version 2.2 of the driver (not the beta) the "09-07-14 16:16:55,953 WindowServer[96]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fd9a2e10050) - disabling OpenGL"
message is continuously repeating itself. Zapping PRAM hasn't made a difference at all... |
07-15-2014, 02:16 PM | #15 |
Member
Join Date: Aug 2012
Posts: 36
|
Would you care to comment, DisplayLink?
|
07-17-2014, 04:20 PM | #16 |
Mac Team
Join Date: Feb 2009
Posts: 606
|
Hi,
This is a known OS issue, triggered depending on the content being drawn on screen and depending on any SW on the system tracking the screen contents. I'm not aware of behavioural issues arising from these logs. Apple has an internal bug for this, ID 14739701. If you want to raise its priority please open a new bug at bugreporter.apple.com. Cheers, Carlo |
07-29-2014, 12:15 PM | #17 |
Member
Join Date: Aug 2012
Posts: 36
|
I did raise a bug at Apple (17619820), they closed it as a duplicate of another issue (16585152). I can't see the details of other issues, only my own (I don't have a full developer account at Apple).
|
08-15-2014, 08:40 AM | #18 |
Mac Team
Join Date: Feb 2009
Posts: 606
|
Hi D43m0n,
No one external to Apple, even developers, can see other people's issues. This means that once Apple has admitted an issue is theirs nobody has any way to check the status. Through BugReporter at least. There was a developer petition some time ago to raise the priority of this issue with Apple but I guess it fell short of its objective. I've been assured that Apple looks at all issues and the number of reports for the same issue affects its priority so let's do everything we can. Hope. Cheers, Carlo |
09-17-2014, 03:57 PM | #19 | ||
Junior Member
Join Date: Oct 2013
Posts: 18
|
Quote:
This issue is actually more serious than you might think, because the OS is constantly writing to your hard drive which is going to do anything but improve it's longevity. I've got into the habit of running the following in Terminal on every boot, just to stop the constant writing to the disk (which can really add up if you're using the Mac 8 hours+/day): Quote:
Last edited by BMT; 09-17-2014 at 04:02 PM. |
||
09-18-2014, 06:28 AM | #20 | |
Mac Team
Join Date: Feb 2009
Posts: 606
|
Quote:
The new API has benefits but has some issues as well, one of which is the log spamming in some situations. We have raised all issues with Apple. I cannot share any more information on this I'm sorry Cheers Carlo |
|
Tags |
windowserver |
|
|