Where to report bugs?

Discussion in 'NOD32 version 2 Forum' started by Tekl, Jan 13, 2004.

Thread Status:
Not open for further replies.
  1. Tekl

    Tekl Registered Member

    Joined:
    Jan 12, 2004
    Posts:
    16
    Hello,

    what's the best way reporting bugs? Is there a bugtracker like the developers of The Bat use?

    Maybe this post is a bug:
    http://www.wilderssecurity.com/showthread.php?t=19446

    Tekl
     
  2. Paul Wilders

    Paul Wilders Administrator

    Joined:
    Jul 1, 2001
    Posts:
    12,472
    Location:
    The Netherlands
    Tekl,

    Although I for one can't reproduce the issue you are reffering to, support@eset.com is the address to contact.

    regards.

    paul
     
  3. Mele20

    Mele20 Former Poster

    Joined:
    Apr 29, 2002
    Posts:
    2,495
    Location:
    Hilo, Hawaii
    I can reproduce it. I think it may be a bug. Opening the help file causes the worst problem. Memory usage soars and it is most interesting to watch what in the Help file causes memory to soar. Memory is only partially released after using the help file UNLESS you minimize NOD to the task bar and THEN close. Most curious behavior. I don't think I will open the Help file anymore unless I can remember to then minimize to the taskbar before closing. Actually, the best thing to do appears to be to let NOD sit minimized in the task bar after using the Help file as that is the only way nod32.kui will let go of the memory and go down to 300-400kb. At least this how it appears to me. I am no expert so I certainly may be missing something. Can others look at this behavior and perhaps explain why this appears to be occurring?
     
  4. anders

    anders Eset Staff Account

    Joined:
    Oct 25, 2002
    Posts:
    410
    As far as I know, this is a Windows-thing. I've been noticing this in other programs too, (for example, own programs).

    The memory should be stored in the swap when it's not needed, so, it's no major problem. AFAIK, they will be freed if a window is minimized/closed, but not if it's hidden. A simple "solution" to this, would be if the programmers minimized the window first, then hid it, or completely destroyed it.

    Best regards,
    Anders
     
Thread Status:
Not open for further replies.