rhuber
07-20-2014, 10:23 PM
Hi All,
Just thought this might be useful to others. I have been experiencing issues where DisplayLinkManager was using 80% of CPU according to Activity Monitor. It seemed to occur randomly, however I have finally found the cause.
Growl (notification system for OSX) has a feature where it pulses its menubar icon when there are some types of unseen notification. This pulse appears to really cause the DisplayLinkManager process to go crazy (and console.log is spamming the opengl errors at a crazy rate).
Disabling the pulse in Growl prefs has made my day, hopefully this solves a mystery for others....
Just thought this might be useful to others. I have been experiencing issues where DisplayLinkManager was using 80% of CPU according to Activity Monitor. It seemed to occur randomly, however I have finally found the cause.
Growl (notification system for OSX) has a feature where it pulses its menubar icon when there are some types of unseen notification. This pulse appears to really cause the DisplayLinkManager process to go crazy (and console.log is spamming the opengl errors at a crazy rate).
Disabling the pulse in Growl prefs has made my day, hopefully this solves a mystery for others....