EZ-AV v7 memory leak in CAVTRAY.exe?

[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...

 

[Roland Stiner]

Version 7 take up more resources, no question about it.

Roland

 

[Kerry Liles]

I dont mind "more resources" but a memory leak or runaway process is not
acceptable.
I notice from another post that 7.0.1.4 is now released - will try that.
Still no reply from CA tech support.

Version 7 take up more resources, no question about it.

Roland

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...

 

[Kerry Liles]

The memory leak and high cpu usage problems seem to have gone away in
7.0.1.4 FWIW

I dont mind "more resources" but a memory leak or runaway process is not
acceptable.
I notice from another post that 7.0.1.4 is now released - will try that.
Still no reply from CA tech support.

Version 7 take up more resources, no question about it.

Roland

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...

 

[Kerry Liles]

Maybe I was celebrating a bit too early... after running for about 24 hours,
CAVtray.exe is now up to about 300MB of VM - not that brutal, but creeping
upward. At least I haven't seen the cpu spiking that was in the previous
release (0.33)

The memory leak and high cpu usage problems seem to have gone away in
7.0.1.4 FWIW

I dont mind "more resources" but a memory leak or runaway process is not
acceptable.
I notice from another post that 7.0.1.4 is now released - will try that.
Still no reply from CA tech support.

Version 7 take up more resources, no question about it.

Roland

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...