hdsentinel on windows7 x64 w 8GB DRAM + ESET NOD32 AV

[jazzman_jeff]

I have used ESET NOD32 AV for a long time. I have used hdsentinel for a long time as well (I'm a registered user). Since upgrading to ESET AV V5, ESET would climb to about 2GB of memory usage and hang after about 6 hours. It turns out that something hdsentinel does exposes a memory leak in ESET V5 and the V6beta. By exiting HDS this morning, ESET has operated within incident. I'm not saying this is hdsentinal's problem... regardless of how good (or bad) the hdsentinel code is, ESET should behave it'self. That set, I can't help but wonder if HDS is doing something to influence this. As I really like hdsentinel, I thought I would report this so you are aware of it.

[hdsentinel]

Thanks for your message and the information !

Until now, we experienced no issues with ESET AV and personally it is hard to imagine which function(s) of Hard Disk Sentinel can trigger that the memory usage of NOD32 climbs.

Do you see the same increase rate regardless of the detection frequency (when Hard Disk Sentinel checks the status of hard disks), which can be adjusted at Configuration -> Advanced options page?

If possible, please use the Report -> Send test report to developer function as then I can check the status and this may give some ideas.

Thanks!

[stinklyonion]

I also had this problem with NOD32, but when I changed to a different AV, everything changes for good.

[alan-0000]

If ESET hangs after 6 hours of INNOCENT activity by HDS,
can you seriously expect ESET to survive more than a few seconds if vicious malware is attacking.

ESET need to fix their product immediately.

Perhaps you can stir up pressure on their forum
http://www.wilderssecurity.com/forumdisplay.php?f=15