![]() |
|
|
|
|
#1 |
|
Junior Member
Join Date: Feb 2015
Posts: 4
|
Are there any known issues with Firefox on a DisplayLink monitor causing the DisplayLinkManager process to consume excessive CPU?
I found that when I have Firefox running on my DisplayLink monitor, that the DisplayLinkManager process consumes 50% CPU. If I move Firefox to a non-DisplayLink monitor then the DisplayLinkManager process drops to 15% CPU utilization. I am running the latest Firefox version 35.0.1. Thanks, Shane |
|
|
|
|
|
#2 |
|
Junior Member
Join Date: Feb 2015
Posts: 4
|
I think I just found a solution from the archives of this forum.
Goto Firefox Preferences > Advanced > General and uncheck 'Use hardware acceleration when available'. Now when I have Firefox on my DisplayLink monitor the DisplayLinkManager process consumes less than 5% CPU. reference: http://www.displaylink.org/forum/showthread.php?t=730 |
|
|
|
|
|
#3 |
|
Junior Member
Join Date: Feb 2015
Posts: 1
|
When I upgraded to 10.10.2 /usr/sbin/distnoted agent was eating the machine.
I uninstalled the driver, rebooted, reinstalled the driver, rebooted. Something in the 10.10.1 -> 10.10.2 upgrade process correlated with my problem. Seems okay now ... |
|
|
|
![]() |
|
|