Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Mac Software

Reply
 
Thread Tools Search this Thread Display Modes
Old 05-13-2014, 03:41 AM   #1
magillagorilla
Junior Member
 
Join Date: May 2014
Posts: 5
Question Endless log spam _CGXGLDisplayContextForDisplayDevice: No matching context for device

So I've just put in an Anker USB3 -> HDMI adapter, loaded the latest beta software and it works great.

However my console is now spammed *ENDLESSLY* with

Code:
5/12/14 10:39:21.472 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:21.572 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:21.680 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:21.763 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:21.872 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:21.963 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.022 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.052 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.164 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.281 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.363 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.464 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.564 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.672 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.752 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.881 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:22.964 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:23.022 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
5/12/14 10:39:23.064 PM WindowServer[295]: _CGXGLDisplayContextForDisplayDevice: No matching context for device (0x7fbae3402cd0) - disabling OpenGL
About 12 lines a second, it doesn't stop.

Any suggestions on how to stop?

I'm on 10.9.2
magillagorilla is offline   Reply With Quote
Old 05-13-2014, 11:52 AM   #2
magillagorilla
Junior Member
 
Join Date: May 2014
Posts: 5
Default

Well, I'm not sure what I did to fix this, but after several reboots and clearing nvpram, the log messages have stopped. (cmd-option-p-r during boot before grey screen)

Hope it stays that way.
magillagorilla is offline   Reply With Quote
Old 05-15-2014, 02:13 PM   #3
MickM
Member
 
Join Date: Oct 2011
Posts: 52
Default

So what you have observed is THE primary reason I've been avoiding the 2.2 beta all this time. I have a solid state drive and the last thing I need is a dozen long lines PER SECOND and forever written to a log file. Someone previously said the log files are capped in size so it shouldn't be a problem - but that's beside the point. Yes they are capped in size, but they are still endlessly overwritten as the never ending stream of console output continues (and wearing out my SSD).

I tried your suggestion about zapping the PRAM and it did help! Now the console spew isn't continuous, but comes in big spurts whenever anything in the DisplayLink monitor happens (e.g. moving a window, scrolling in a window, Expose etc.). Fortunately moving the mouse around in the DisplayLink monitor doesn't trigger the console spew. It's a lot better now, but it definitely still needs fixing.
MickM is offline   Reply With Quote
Old 05-15-2014, 02:39 PM   #4
magillagorilla
Junior Member
 
Join Date: May 2014
Posts: 5
Default

Oh man... I just went back in to check, since you said that and it's still happening. My ASL logs yesterday are about 2gb ARGH!!!

This is completely unacceptable. I assume you don't have this problem with an earlier release? I'm thinking about trying an older driver. I can't do this to my system.
magillagorilla is offline   Reply With Quote
Old 05-15-2014, 02:55 PM   #5
MickM
Member
 
Join Date: Oct 2011
Posts: 52
Default

After I zapped the PRAM I installed the latest 2.2 beta and now I only get the spew when stuff happens in the DisplayLink window. There are actually several of the same error messages even when I do things in other non-DisplayLink displays, but at least now it's not continuously, relentlessly flooding the console - now it's just activity based. It's still bad and needs fixing, but it's much better. Who knows, it might all start up again like it did with you - if that happens then I'll be uninstalling 2.2 and going back to 2.1 again (with all of it's awful display jittering that 2.2 seems to have fixed).

The only reason I'm using a DisplayLink solution is because, even after all this time, a lightning hub that's even remotely affordable just doesn't exist :-(.
MickM is offline   Reply With Quote
Old 05-15-2014, 03:14 PM   #6
magillagorilla
Junior Member
 
Join Date: May 2014
Posts: 5
Default

Well I just cleared my asl logs, and went to 2.1 drivers. So far no logspam. 2.1 drivers so far seem to work just as well as 2.2.
magillagorilla is offline   Reply With Quote
Reply

Tags
windowserver

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 10:36 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, vBulletin Solutions, Inc.