Why is nicitdl.exe hogging my CPU

[Jeff in Pleasanton]

I have never knowing launched DSC, and I know nothing about attaching and detaching databases using MAX.  But I do know that nicitdl.exe has been hogging my CPU cycles, sometimes jumping to 70% even when LabVIEW is not running.  I uninstalled DSC, which is like amputating your leg to fix a toenail, but at least my machine is more responsive now.

What can I do to install and configure DSC such that it doesn't hijack my CPU?

[unclebump]

What version are you using?? Have you applied any fixes that are available??

http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C0CF1?opendocument&node=132070_US 

[Jeff in Pleasanton]

I've updated everything to the latest 8.0.1 quaterly release.  It looks like the available fix is just the 8.0 to 8.0.1 fix?

http://digital.ni.com/softlib.nsf/websearch/E7E0A9231F42E511862570EB0060E7FF ?

[jdr_ni]

Heavy CPU usage by the Citadel service usually means one of two things are happening:

1) A large number of Alarms or Events are being logged or have recently been logged.
2) Data is being copied to a remote machine, either because an application running in the shared variable engine is configured to log data remotely, or because a remote machine is querying your machine for historical data.

Variables and servers deployed to the Variable Engine will continue to run even when you exit LabVIEW. If you want the system to be completely idle, you will need to explicitly undeploy your libraries prior to exiting LabVIEW.

JD Robertson
Software Engineer
National Instruments