Promise RAID message agent memory leak

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

I am using the A7V8X with the onboard Promise FastTrak 376 RAID SATA
controller. I have been using the Promise monitoring utility that installs
the "Promise RAID message agent" service, but this has a serious memory leak
on Windows 2000.

I installed the Version 3.2.1 Build 8 that shipped on the CD and have also
downloaded Build 11 from ASUS's site, but both are leaking and causing my
system with 1GB of RAM to run out of memory in a couple of days.

I have verified the leak to be the "Promise RAID message agent" via a lot of
monitoring with Perfmon. When I don't start the service, handles and
non-paged pool bytes stay level, but when I start the service the non-paged
pool bytes and handle ramp up until I run out of memory.

I know it is not nessessary to run the service to have RAID, but I still
would like to have it available to monitor the drives. Is there any fix?

 

[Tim]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Is there a supported way to stop the process?
What happens if you end task it?
Might you run the process only when it is needed and shutdown when finished?

Have you posted a message to Promise about this - they should be able to fix
quickly (although it can be difficult).

- Tim


"news.lightship.net" <nojunk_allowed@nospam.com> wrote in message
news:nNXfc.16201$pk5.7498@fe03.usenetserver.com...
> I am using the A7V8X with the onboard Promise FastTrak 376 RAID SATA
> controller. I have been using the Promise monitoring utility that
installs
> the "Promise RAID message agent" service, but this has a serious memory
leak
> on Windows 2000.
>
> I installed the Version 3.2.1 Build 8 that shipped on the CD and have also
> downloaded Build 11 from ASUS's site, but both are leaking and causing my
> system with 1GB of RAM to run out of memory in a couple of days.
>
> I have verified the leak to be the "Promise RAID message agent" via a lot
of
> monitoring with Perfmon. When I don't start the service, handles and
> non-paged pool bytes stay level, but when I start the service the
non-paged
> pool bytes and handle ramp up until I run out of memory.
>
> I know it is not nessessary to run the service to have RAID, but I still
> would like to have it available to monitor the drives. Is there any fix?
>
>
>
>