PDA

View Full Version : memory hog?



lost_in_vegas
2010-04-15, 02:03
ok, the last few updates had spybot eating up over
120 megs of memory.
before the latest update, it was at 72 megs,
and after todays update, its now at over 115.

whats going on with the different megs usage?
is 72 normal? is it over 115 normal?

im using spybot search & destroy
version 1.6.2.46
latest detection update 4/14/2010

as i said, before the latest update, i was using like
72 megs worth of memory, now, its over 115.

drragostea
2010-04-15, 03:36
What are the specs of your machine?

lost_in_vegas
2010-04-15, 05:43
win xp
media center edition
version 2002
sp#3
toshiba satellite

and its the tea timer part that seems to
be the problem in all this.

let me know if you need more info on
the machine.!

spybotsandra
2010-04-15, 11:23
Hello,

When the computer is running for a long time without a standby, reboot, or shutdown memory consumption of a (refers to any) can slightly increase.

It's taking that much because TeaTimer is a Resident Shield that actively protects you from malware. I would suggest you reboot and see how it goes. Usually TeaTimer will take up 35-50MB of RAM. Seeing that modern PCs built today have more RAM and resources, 80MB should be nothing.

If this does not help you can disable TeaTimer as follows:
- Go into Spybot - Mode - Advanced Mode - Tools - Resident.
- Uncheck the following: Resident "TeaTimer" (Protection of over-all system settings) Active.

Best regards
Sandra
Team Spybot

lost_in_vegas
2010-04-16, 01:01
like i said, before this latest update, it was using 72megs
now, its using upwards over 113 - the tea timer. So
If I read this right, it's using the higher end of normal?

its just strange from update to update, theres such a wide
range of memory usage.

drragostea
2010-04-16, 04:52
I found an interesting thread, this is related to your query:
http://forums.spybot.info/showthread.php?t=55016
-
I run my ancient P4 3.0Ghz 1.5GB of DDR RAM with TeaTimer on and that was more than enough to supply TeaTimer with what it needs. If I assume correctly, that your machine is newer than mine, then your resources certainly should have no problems giving Teatimer what it needs.

Unless you are a heavy multitasking or run resource intensive programs, I do not see why this is a problem.

IamJim
2010-04-17, 13:32
drragostea and Sandra... neither of these address the issue he has posted...

As I also experience the same thing... As for accumulating and rebooting...that's not the issue.

As he stated... was using 72meg area... Now back over 100+ for me also.

Thing is, for about a year...it has been creeping up...

2 downloads ago...(or so...it dropped back to what I consider normal)... the 72 meg area..

I got the 4-14 download...and now Teatime back up to 105 and VM 124meg.

I also noticed a serious jump in detection file size? this was 5 meg it said and I know for some time has been 3 meg.

Please advice....

Also, moire memory is not an option... cleaner coding fixes that...(smile)

Again, mentioning it...as I have been debatinng removal....but when I was back to 70meg are of your usage...

I figured the problem was fixed.

Jim

Matt
2010-04-17, 15:38
I also noticed a serious jump in detection file size? this was 5 meg it said and I know for some time has been 3 meg.
Reason:
Scanner Upgrade for the Virtumonde Trojan

IamJim
2010-04-17, 15:54
Reason:
Scanner Upgrade for the Virtumonde Trojan

Thank you for this info.

Jim

tooltime63
2010-05-06, 18:53
Teatimer.exe must have a memory leak issue. When it first starts it takes about 105MB RAM once it settles down. I'm on Dual Core 3Ghz with 4GB RAM on Win 7. After my machine has been running for about 4 days, teatimer memory usage is almost 1GB! The only resolution is too reboot or stop/restart teatimer.exe.

TextCrab
2010-05-08, 20:58
I am having the same problem with TeaTimer.

When I check my running process’s, TeaTimer.exe is always using about 114 Mb of memory. And it doesn’t slowly build up to this, I can end the process and restart TeaTimer and it will start itself at 114,000 K of memory usage.