1.4 consume all CPU ( ViscocityHelper ) - OSX 10.8 )

[dyerucf]

Whenever I start my VPN connection ViscocityHelper spawns n+1 processes, which consumes all CPU. I actually have to drop to console in order to regain control of my system.

Console Logs: https://gist.github.com/d994254378a78a3a148c

Example of the spawened proceses

Code: Select all

root           53589   6.8  0.2   660108  13660   ??  Rs   11:49AM   0:00.51 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53453   6.7  0.3   672624  28528   ??  Rs   11:49AM   0:00.88 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53481   6.6  0.3   667676  23796   ??  Rs   11:49AM   0:00.79 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53416   6.5  0.4   677744  33608   ??  Rs   11:49AM   0:00.94 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53677   6.2  0.1   637620   5640   ??  Us   11:50AM   0:00.15 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53665   6.2  0.1   637620   5632   ??  Us   11:50AM   0:00.19 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53720   6.1  0.0   603228   2560   ??  Us   11:50AM   0:00.04 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53576   6.1  0.2   661388  14920   ??  Rs   11:49AM   0:00.57 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53398   6.0  0.4   680720  36060   ??  Ss   11:49AM   0:01.02 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53459   6.0  0.3   671600  27664   ??  Rs   11:49AM   0:00.87 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53580   5.9  0.2   660364  13968   ??  Rs   11:49AM   0:00.55 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53448   5.9  0.4   675184  31800   ??  Rs   11:49AM   0:00.92 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53699   5.8  0.1   637364   5412   ??  Rs   11:50AM   0:00.11 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53490   5.8  0.3   668680  23636   ??  Rs   11:49AM   0:00.78 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53683   5.5  0.1   636596   5536   ??  Us   11:50AM   0:00.13 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net
root           53429   5.2  0.4   675696  30920   ??  Rs   11:49AM   0:00.91 /Applications/Viscosity.app/Contents/Resources/ViscosityHelper setDNS 10.6.3.1 4.2.2.2 10.6.3.2 10.90.3.1 10.6.3.1 10.6.3.2  orl.voxeo.net orl.voxeo.net


Any idea what this is about?

[James]

Hi dyerucf,

Please make sure you don't have OpenDNS's DNSCrypt application installed - it doesn't play well with VPN clients.

If you don't have DNSCrypt installed, then Viscosity is most likely fighting with another application for control of DNS, so it may be worth checking to see if something else could be modifying your DNS settings.

As an alternative solution, if you don't need DNS support, you could turn it off for your connection (under the Networking tab when editing your connection).

Cheers,
James

[dyerucf]

I dont have DNSCrypt installed, not sure what else could be trying to "modify" my dns.... Any pointers on how to troubleshoot this? I also do need DNS, so unchecking it is not really an option.... Also its worth mentioning that this worked fine in 1.3

[dyerucf]

Any thoughts? Right now my VPN is useless... would appreciate a response on how to handle this as soon as possible.

[James]

Hi dyerucf,

Judging from your Console log Viscosity keeps detecting that the DNS servers set are not the same as specified for your VPN connection. This is the same behaviour we see when another application (such as DNSCrypt) keeps changing them.

Any ideas of anything else that could be attempting to change your DNS servers (or perhaps changing your network location)? Do you have Internet Sharing turned on, or anything like that? Check the Console (without searching/filtering for just messages from Viscosity/openvpn) to see if there are any messages that could indicate what is going on (although I checked your posted Console log without seeing anything obvious), and perhaps check the list of processes running using the Activity Monitor application (make sure All Processes is selected) to see if you can tell what Viscosity is fighting with for DNS control (the other process will likely have high CPU activity as well).

Cheers,
James

[James]

Hi Guys,

We've figured out what is going on here - the high CPU usage and DNS fighting can also occur if you have set the same DNS server more than once. The latest beta version now includes a workaround for this problem, or it can be resolved by removing the duplicate DNS server entry from under the Networking tab when editing your connection.
viewtopic.php?p=134#p134

Cheers,
James