6.2: CPU spikes on Longitude agent

We have seen some cases in Longitude 6.2 in which the CPU on a Longitude agent will spike when collecting data for Internet Macros. The Firefox instances used to collect data for the Internet Macro do not close correctly, leaving orphaned Firefox processes on the agent.

Until a patch is available, this problem can be addressed by restarting the Longitude Statistics Server component. This should kill the orphaned Firefox processes, but you may need to check the Longitude server directly and close dialog boxes for Firefox errors.

Please note - if the agent used for the collections is the Management Console, the Rule Engine component may also be using excessive CPU. Please restart this component also.