CPU being overworked by displaylinkmanager on 1.7 beta 3

[lambretta]

Hi.

I did the beta 3 upgrade this morning and noticed a task in my Activity Monitor called displaylinkmanager was using in excess of 100% of the CPU consistently. I killed it using quit process and my monitor went off (the one using the display link adapter) and then came back on. The DisplayLInkManager process is still there but now only uses around 0.6% of the CPU.

This is my info, I bought the MBP about 2 years ago...

Model Name: MacBook Pro
Model Identifier: MacBookPro5,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB

Hope this is useful, keep up the good work

[tsihh]

Hi,

I had the same issue couple of days ago. After disconnecting and reconnecting the cpu usage went down

Model Name: MacBook
Model Identifier: MacBook5,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 3 MB
Memory: 6 GB


Rgds,
Ahti

[ChristianP]

Thanks for your report. We are trying to reproduce this issue. Does the problem happen at every restart or sleep/wakeup? If you are able to reproduce the issue easily, could you please download the new debug tool here http://www.displaylink.com/support/ticket.php?id=269 and post the output file?. Switch first the log verbosity of the driver to DEBUG from the advanced menu (unplug and replug the adapter) , try to reproduce the issue and collect the information. Switch back the log verbosity to Info when fished. Thanks

[lambretta]

Originally Posted by ChristianP

Thanks for your report. We are trying to reproduce this issue. Does the problem happen at every restart or sleep/wakeup? If you are able to reproduce the issue easily, could you please download the new debug tool here http://www.displaylink.com/support/ticket.php?id=269 and post the output file?. Switch first the log verbosity of the driver to DEBUG from the advanced menu (unplug and replug the adapter) , try to reproduce the issue and collect the information. Switch back the log verbosity to Info when fished. Thanks

I can't get it to happen again, so it must just be something that happened once after the installation?

I've tried a reboot and a sleep but all is well on the CPU front.

[ChristianP]

Ok, thanks for your answer.
We are still trying to identify the conditions that cause this behavior. If you happen to see the issue again, please report it. Thanks

[lambretta]

Originally Posted by ChristianP

Ok, thanks for your answer.
We are still trying to identify the conditions that cause this behavior. If you happen to see the issue again, please report it. Thanks

Happened again this morning, very strange as I don't think I did anything different...

I used my laptop all weekend at home, without any external displays, then came into work, plugged in my displaylink USB adapter and the monitor via the display mort and the displaylink screen wasn't working properly (missing bits of graphics and generally being unresponsive) so I waited for the backup to complete then shut down the system. After restarting I think had to put it to sleep to stop the drag no drop thing from happening, and then I noticed the fans going mental - quick check of activity monitor and sure enough its that same process.



I force quit the process and when it came back on it was fine.

[ChristianP]

Originally Posted by lambretta

Happened again this morning, very strange as I don't think I did anything different...

I used my laptop all weekend at home, without any external displays, then came into work, plugged in my displaylink USB adapter and the monitor via the display mort and the displaylink screen wasn't working properly (missing bits of graphics and generally being unresponsive) so I waited for the backup to complete then shut down the system. After restarting I think had to put it to sleep to stop the drag no drop thing from happening, and then I noticed the fans going mental - quick check of activity monitor and sure enough its that same process.



I force quit the process and when it came back on it was fine.

Thanks for your detailed report. We are trying to solve issue, even if it's not easy to replicate it. Any further information you get on how to reproduce it will be very helpful. Thanks