K
Kerry Liles
Anyone else experiencing severe problems (over a period of a couple of
hours) with CAVTRAY.exe using excessive amount of cpu and ever-increasing
virtual memory footprint? When the tray app starts it has a vm footprint of
of about 34.8MB - after a couple of hours or so [after a few
autodownloads??] it increases to ~200MB and keeps climbing. Meanwhile cpu
utilization of that task (kernel cpu) hits 70+% and stays there almost
constantly. Killing the process (or even the process tree) via procexp (from
Sysinternals) somehow does not really seem to remove the task from the
machine - although it no longer appears in the list. Meanwhile the machine
crawls...
I've sent this to Sammy at CA but no response yet - wondering if others have
seen the same thing...
on XP pro - NOT SP2...
hours) with CAVTRAY.exe using excessive amount of cpu and ever-increasing
virtual memory footprint? When the tray app starts it has a vm footprint of
of about 34.8MB - after a couple of hours or so [after a few
autodownloads??] it increases to ~200MB and keeps climbing. Meanwhile cpu
utilization of that task (kernel cpu) hits 70+% and stays there almost
constantly. Killing the process (or even the process tree) via procexp (from
Sysinternals) somehow does not really seem to remove the task from the
machine - although it no longer appears in the list. Meanwhile the machine
crawls...
I've sent this to Sammy at CA but no response yet - wondering if others have
seen the same thing...
on XP pro - NOT SP2...