CopperLan

sometimes the cpvnmd uses 100% CPU on one core

i can't really tell when and why it's happening .. it's on my macPro and my MBP

i can just kill it and then it's automatically restarting itself and all is good for some time

anyone here?

Hello,

The first thing to do is to check if this issue still occurs if you disconnect any USB MIDI controller.

This kind problem is generally due to a broken 3rd party MIDI port handler after a MacOSX update. Some users using Korg or AVID hardware already reported this issue, and successfully fixed it by installing an updated version of their Korg or AVID software matching the new MacOSX version.

It has been also reported rarely in case of heavy Sysex transmission. Is it the case?

i have no Korg or Avid Software Installed .... but for sure a couple of USB Drivers for elektron-synth, roland and quite some others ...
i'm doing nothing when it happens .. so heavy sysex transmission doesn't seem to be the reason here

so i'll disconnect all usb-midi-devices and update the drivers where possible and see if it helps

.... and check that Elektron or Roland drivers are compatible with your MacOSX version. It happens that a driver is broken when you upgrade MaxOSX, and there is no notification about that. In this case, the system function we are using to open the MIDI port just freeze... and we have no way to guess that before trying to open the port.

it's hard to debug as it's not happening on a regular basis ... but today i started my MBP and the cpvnmd directly started using 100% cpu .. nothing was plugged into the MBP.

There's one thing wich i think could be a reason: i plugged in a networkcable via and usb-c adapter - and so the networkconfig was changing and i also plugged in an usb-harddrive

but both things are a typical scenario for me.. and the problem is not always appearing. pretty strange.

i foudn a log from cpvnmd ... i couldn't see any useful information for me

mmmhh... yes indeed the log file looks like the network receive thread is locked for some reason. Indeed, it could be related to a problem around the network interface. We already had to manage a similar issue with a Thunerbolt Ethernet plugged in the MacBook after the wake up from sleep while it was plugged in when going into sleep mode. The problem is not related to the network itself, it's safe to disconnect/reconnect from any network, but it seems that CopperLan is not notified and/or can't manage properly the events occurring on network interface changes on Mac.

I'll try to reproduce and fix, but in the meantime please check that your network interface is connected before waking up the computer.

i didn't happen over the last week .. so it seems not so terrible as i thought initially