Mac OSX 1.7b3 maxing out processor

[heinmuek]

Have just moved up from beta2 because of my MacBook Pro not waking up with DisplayLink installed. That problem seems to be fixed but now after the required restart the processor(s) are over running at 100%+.
Going into Activity Monitor & quitting the DisplayLink process kills the CPU overload & DisplayLink still seems to work as my second monitor responds just fine.
Putting the Mac to sleep & waking it does not cause any problems either i.e. both monitors wake up without a hitch. My main monitor is attached via the mini display port.

[ChristianP]

Originally Posted by heinmuek

Have just moved up from beta2 because of my MacBook Pro not waking up with DisplayLink installed. That problem seems to be fixed but now after the required restart the processor(s) are over running at 100%+.
Going into Activity Monitor & quitting the DisplayLink process kills the CPU overload & DisplayLink still seems to work as my second monitor responds just fine.
Putting the Mac to sleep & waking it does not cause any problems either i.e. both monitors wake up without a hitch. My main monitor is attached via the mini display port.

If you are able to easily reproduce the high CPU usage, could you please use the debug tool here http://www.displaylink.com/support/ticket.php?id=269 and post the output? Change first the log verbosity to "Debug", reproduce the issue and collect the log information. After collecting the information remember to set the verbosity back to Info. Thanks