Jump to content

Every Day For 45 Min Immunet Use 100Mb Ram


Recommended Posts

One time every day for 40-45 min imunet uses 100 mb ram(agent) and then goes to 10. I think it has something to do with clamav updates, but i have clamav engine to off and definition updates to off.

I see in logfile that clamav tries to update even i have definition updates to off.

Link to comment
Share on other sites

Block mode is off. Immunet free version 3.0.

 

 

I think is something relating to the updates of clamav but i have clamav engines and updates to off. In the log file of clamav when i have a lot of memory usage of immunet i check clamav logfile:

 

2011-03-15 18:37:02 - [Executing 'freshclam.exe --stdout --config-file=C:\Program Files\Immunet\clamav\freshclam.conf" --datadir="C:\Program Files\Immunet\clamav&quot]

2011-03-15 18:37:02 - [state is now: FRESH_PRE]

2011-03-15 18:37:03 - [GOT: ClamAV update process started at Tue Mar 15 18:37:03 2011]

2011-03-15 18:37:03 - [sEND: state: UPD_CHECK - status: success - file: - pct: 0%]

2011-03-15 18:37:03 - [state is now: FRESH_IDLE]

2011-03-15 18:37:03 - [GOT: WARNING: Your ClamAV installation is OUTDATED!]

2011-03-15 18:37:03 - [GOT: WARNING: Local version: clamav-0.97w Recommended version: 0.97]

2011-03-15 18:37:03 - [GOT: DON'T PANIC! Read http://www.clamav.net/support/faq'>http://www.clamav.net/support/faq'>http://www.clamav.net/support/faq'>http://www.clamav.net/support/faq'>http://www.clamav.net/support/faq'>http://www.clamav.net/support/faq'>http://www.clamav.net/support/faq]'>http://www.clamav.net/support/faq]'>http://www.clamav.net/support/faq]'>http://www.clamav.net/support/faq]

2011-03-15 18:37:03 - [GOT: main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven)]

2011-03-15 18:37:03 - [GOT: Downloading daily-12839.cdiff [ 24%]]

2011-03-15 18:37:03 - [sEND: state: UPD_NEWER_FOUND - status: success - file: - pct: 0%]

2011-03-15 18:37:03 - [sEND: state: UPD_DOWNLOAD_BEGIN - status: success - file: - pct: 0%]

2011-03-15 18:37:03 - [sEND: state: UPD_FILE_BEGIN - status: success - file: daily-12839.cdi - pct: 0%]

2011-03-15 18:37:03 - [state is now: FRESH_DOWN]

2011-03-15 18:37:03 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12839.cdi - pct: 24%]

2011-03-15 18:37:03 - [GOT: Downloading daily-12839.cdiff [ 50%]]

2011-03-15 18:37:03 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12839.cdi - pct: 50%]

2011-03-15 18:37:03 - [GOT: Downloading daily-12839.cdiff [ 76%]]

2011-03-15 18:37:03 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12839.cdi - pct: 76%]

2011-03-15 18:37:03 - [GOT: Downloading daily-12839.cdiff [100%]]

2011-03-15 18:37:03 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12839.cdi - pct: 100%]

2011-03-15 18:37:04 - [GOT: Downloading daily-12839.cdiff [100%]]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12839.cdi - pct: 100%]

2011-03-15 18:37:04 - [GOT: Downloading daily-12840.cdiff [100%]]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_COMPLETE - status: success - file: daily-12839.cdi - pct: 100%]

2011-03-15 18:37:04 - [state is now: FRESH_IDLE]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_BEGIN - status: success - file: daily-12840.cdi - pct: 0%]

2011-03-15 18:37:04 - [state is now: FRESH_DOWN]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12840.cdi - pct: 100%]

2011-03-15 18:37:04 - [GOT: Downloading daily-12840.cdiff [100%]]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12840.cdi - pct: 100%]

2011-03-15 18:37:04 - [GOT: Downloading daily-12841.cdiff [100%]]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_COMPLETE - status: success - file: daily-12840.cdi - pct: 100%]

2011-03-15 18:37:04 - [state is now: FRESH_IDLE]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_BEGIN - status: success - file: daily-12841.cdi - pct: 0%]

2011-03-15 18:37:04 - [state is now: FRESH_DOWN]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:04 - [GOT: Downloading daily-12841.cdiff [100%]]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_PROGRESS - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:04 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 18:37:04 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 18:37:04 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 18:37:04 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 18:37:04 - [GOT: daily.cld updated (version: 12841, sigs: 73375, f-level: 60, builder: ccordes)]

2011-03-15 18:37:04 - [sEND: state: UPD_FILE_COMPLETE - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:04 - [state is now: FRESH_IDLE]

2011-03-15 18:37:04 - [GOT: WARNING: Your ClamAV installation is OUTDATED!]

2011-03-15 18:37:04 - [GOT: WARNING: Current functionality level = 59, recommended = 60]

2011-03-15 18:37:04 - [GOT: DON'T PANIC! Read http://www.clamav.net/support/faq]

2011-03-15 18:37:04 - [GOT: bytecode.cvd is up to date (version: 142, sigs: 40, f-level: 60, builder: acab)]

2011-03-15 18:37:04 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 18:37:04 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 18:37:04 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 18:37:04 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 18:37:04 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 18:37:04 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 18:37:04 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 18:37:06 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 18:37:06 - [GOT: Database updated (919629 signatures) from db.local.win.clamav.net (IP: 150.214.142.197)]

2011-03-15 18:37:06 - [state is now: FRESH_RELOAD]

2011-03-15 18:37:06 - [GOT: (null)]

2011-03-15 18:37:06 - [sEND: state: UPD_DOWNLOAD_COMPLETE - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:06 - [sEND: state: UPD_INSTALL_BEGIN - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:06 - [sEND: state: UPD_INSTALL_COMPLETE - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:06 - [sEND: state: UPD_DONE - status: success - file: daily-12841.cdi - pct: 100%]

2011-03-15 18:37:06 - Log file closed

2011-03-15 19:37:08 - Log file initialized

2011-03-15 19:37:13 - [Executing 'freshclam.exe --stdout --config-file=C:\Program Files\Immunet\clamav\freshclam.conf" --datadir="C:\Program Files\Immunet\clamav&quot]

2011-03-15 19:37:13 - [state is now: FRESH_PRE]

2011-03-15 19:37:13 - [GOT: ClamAV update process started at Tue Mar 15 19:37:13 2011]

2011-03-15 19:37:13 - [sEND: state: UPD_CHECK - status: success - file: - pct: 0%]

2011-03-15 19:37:13 - [state is now: FRESH_IDLE]

2011-03-15 19:37:13 - [GOT: WARNING: Your ClamAV installation is OUTDATED!]

2011-03-15 19:37:13 - [GOT: WARNING: Local version: clamav-0.97w Recommended version: 0.97]

2011-03-15 19:37:13 - [GOT: DON'T PANIC! Read http://www.clamav.net/support/faq]

2011-03-15 19:37:13 - [GOT: main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven)]

2011-03-15 19:37:13 - [GOT: daily.cld is up to date (version: 12841, sigs: 73375, f-level: 60, builder: ccordes)]

2011-03-15 19:37:13 - [GOT: bytecode.cvd is up to date (version: 142, sigs: 40, f-level: 60, builder: acab)]

2011-03-15 19:37:13 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 19:37:13 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 19:37:13 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 19:37:13 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 19:37:13 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 19:37:13 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 19:37:13 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 19:37:15 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 19:37:15 - [GOT: (null)]

2011-03-15 19:37:15 - [sEND: state: UPD_NONE - status: success - file: - pct: 0%]

2011-03-15 19:37:15 - Log file closed

2011-03-15 20:37:17 - Log file initialized

2011-03-15 20:37:22 - [Executing 'freshclam.exe --stdout --config-file=C:\Program Files\Immunet\clamav\freshclam.conf" --datadir="C:\Program Files\Immunet\clamav&quot]

2011-03-15 20:37:22 - [state is now: FRESH_PRE]

2011-03-15 20:37:22 - [GOT: ClamAV update process started at Tue Mar 15 20:37:22 2011]

2011-03-15 20:37:22 - [sEND: state: UPD_CHECK - status: success - file: - pct: 0%]

2011-03-15 20:37:22 - [state is now: FRESH_IDLE]

2011-03-15 20:37:22 - [GOT: WARNING: Your ClamAV installation is OUTDATED!]

2011-03-15 20:37:22 - [GOT: WARNING: Local version: clamav-0.97w Recommended version: 0.97]

2011-03-15 20:37:22 - [GOT: DON'T PANIC! Read http://www.clamav.net/support/faq]

2011-03-15 20:37:22 - [GOT: main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven)]

2011-03-15 20:37:22 - [GOT: daily.cld is up to date (version: 12841, sigs: 73375, f-level: 60, builder: ccordes)]

2011-03-15 20:37:22 - [GOT: bytecode.cvd is up to date (version: 142, sigs: 40, f-level: 60, builder: acab)]

2011-03-15 20:37:22 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 20:37:22 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 20:37:22 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 20:37:22 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 20:37:22 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 20:37:22 - [GOT: [LibClamAV] *** This version of the ClamAV engine is outdated. ***]

2011-03-15 20:37:22 - [GOT: [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq ***]

2011-03-15 20:37:23 - [GOT: [LibClamAV] ***********************************************************]

2011-03-15 20:37:23 - [GOT: (null)]

2011-03-15 20:37:23 - [sEND: state: UPD_NONE - status: success - file: - pct: 0%]

2011-03-15 20:37:23 - Log file closed

Link to comment
Share on other sites

Hi,

When I updated Immunet Protect Free v.2.0.17.31 into v.3.0.0.18, I selected first the alternative with ClamAV included. Immediately, I found that Immunet works now slower than before. So I installed Immunet Protect FREE v. 3.0.0.18 without the ClamAV instead. Now Immunet is working as a charm, as before!

Cheers,

sweidre

PS. I have Win 7 Pro x64 SP1 DS.

Link to comment
Share on other sites

Same thing what I experienced.

 

I didn't know Immunet before version 3.0. I am running it (free version) on several machines now, Windows 7 x64 SP1, Windows 7 x86 SP1, Windows XP x86 SP3, with and without ClamAV, along with other AV-Software (AVAST, Trend Micro) and without (that's where Clam is/was activated). What I experienced was that it usually takes between 70 and 100 MB of RAM, sometimes below 10, but I couldn't figure out when and why. So I was already wondering, why people call it "light" on resources. It's good to hear that this is considered a bug. My free Threatfire installation running alongside with Immunet on one machine only takes 2,8MB RAM.

Immunet 3.0 seems to be really fast as long as Clam is not activated. On an older XP Installation (Pentium 4, 2,6 GHz), the Clam-enabled installation hogged on the CPU and specially while browsing the internet or during installations it slowed down the machine a lot. Disabling Clam made it run smooth again. Personally I tend to accuse Clam itself for this problem since I remember the time I tried Winpooch for using ClamWin for on access scanning which was very slow compared to other AV-Software.

 

Off topic question:

Are Threatfire and Immunet comparable or do they compensate weeknesses of the other in the free versions?

Link to comment
Share on other sites

hi everyone,

 

prior to reading this thread, Immunet 3.0 also takes up about 100 MB memory. it is running on Windows XP SP3 x86, with AVG Free Edition 2011. i did not choose to install ClamAV. but i found out under Settings > Detection Engines > ClamAV, i can turn it on or off. it was off, but the program is still running with 100 MB memory.

 

after reading this thread i decided to turn off Monitor Program Install, Monitor Program Start, and Blocking Mode, under General Settings > Protection.

 

now, the program is running anywhere from 15-35MB, pretty consistent at around 24-28MB.

Link to comment
Share on other sites

hi everyone,

 

prior to reading this thread, Immunet 3.0 also takes up about 100 MB memory. it is running on Windows XP SP3 x86, with AVG Free Edition 2011. i did not choose to install ClamAV. but i found out under Settings > Detection Engines > ClamAV, i can turn it on or off. it was off, but the program is still running with 100 MB memory.

 

after reading this thread i decided to turn off Monitor Program Install, Monitor Program Start, and Blocking Mode, under General Settings > Protection.

 

now, the program is running anywhere from 15-35MB, pretty consistent at around 24-28MB.

Hi qiyouguaidao,

Hmm... To turn off Monitor Program Install & Monitor Program Start is not advisable! Turning off these two items means that you are out of shields!

Cheers,

sweidre

Link to comment
Share on other sites

heh thanks Sweidre - yeah by disabling Monitor Program Install & Monitor Program Start you're basically disabling almost all of Immunet.

 

One thing we noted about this bug was that after the first scan memory usage drops back down to under 5MB. So really, all you need to do is let Immunet run as per normal and as soon as it scans anything the extra memory will be released.

Link to comment
Share on other sites

Hi qiyouguaidao,

Hmm... To turn off Monitor Program Install & Monitor Program Start is not advisable! Turning off these two items means that you are out of shields!

Cheers,

sweidre

 

hi sweidre,

 

i did run several tests, with different options turned on or off, all on, and all off. it turned out that the 3 under General Settings weren't the problem why Immunet took up 100 MB of memory. (i'm pretty sure) it was ClamAV. in the free version, when ClamAV was off, Memory consumption ranges from 15-30MB, consistent at around 20-25MB or thereabout. when ClamAV was on, the memory consumption rose within 10 seconds from 24-25MB to 100MB or thereabout. it might have something to do with ClamAV's processing power need itself, or its resident-shield-like capability...

 

i turned off Monitor Program Install & Monitor Program Start, because i felt that i don't need a safety-net program to keep scanning other program/s before installation, and to scan before other program/s start.

 

3 other possible scenarios out of several, regarding prior running of unknown program/s or questionable program/s.

 

  • if i will be running unknown program/s or questionable program/s, there are other options to be safe. for example, creating a virtual space (virtualization) via Oracle's Virtual Box, or some other program similar to that, on a separate partition. if there's a virus, i can simply delete that clean and revert back to normal. saving me plenty of time from potential future conflicts/infections.
  • if one runs backup on a regular basis, if there is anything wrong (like after i uninstalled Immunet 3.0), i can restore my backup, and have things back to normal quickly, instead of depending on system restore, or reinstallation.
  • if one has more than 1 computer, and 1 of those is specially set up for testing n playing with unknown/questionable/naughty stuffs, well, worse come to worst, i can just DNuke/DBan it, or do a clean re-install. :lol:

 

at the moment, i am guessing that Immunet is more suitable for users who have intermediate or beginner knowledge in computer system, like PC. or users that want things simplified (rather than complicated). the program is a cool concept, but i had to remove it for the moment because i have yet to figure out why the program's Self Protect driver failed to load and i got a tight schedule. but i'll return and test it again on this PC later.

 

cheers,

Andrias

Link to comment
Share on other sites

Hi qiyouguaidao,

Of course, it is alright to test what happens, if you switch on or off certain options! In my mind, at least we need one AV program, that will detect malware, when it enters the computer. As some malwares enter into the computer in a hidden way, it is good to have an AV program, that immediately catches the hidden malwares, when they will start. If the AV will remove the malware (or quarantine it) before it does any harm to other files, we are lucky. Otherwise, we need to go back to a restore point or as in my case use a Norton Ghost of the system drive to go back to the latest prior point of time, when the computer was clean. By using an efficient AV program you do not have to go to a backup. Without any AV at all, you will too late get aware of that the computer has been attacked by a malware. What restore point or ghost should you go back to?

I mean, that we need several safety nets approximately in this order:

1. Firewall

2. AntiMalware (AntiVirus, AntiSpyware etc.)

3. Sandboxie and/or Virtual Space

4. Restore Point or Backup (Ghost) of the system drive

(Some softwares combine point 1, and/or 2 above)

Cheers,

sweidre

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...