PDA

View Full Version : TeaTimer using 100,000+ Kb



goldenthroat
2010-01-30, 04:14
Currently TeaTimer.exe is down to 94,400 K. It was at 122,000 before. It tends to be one of the highest memory usage processes running. There are only 8 other processes running.

I saw something in another post about long lists making it require more RAM. I'm not sure what lists these are, but I just checked the "Black & White List" and the four lists there are all empty.

System info: Dell Dimenstion 8250 (6 years old, but still running)
Pentium(R) 4 CPU 3.06GHz
512 MB of RAM
XP Home Edition Version 2002 SP3
Spybot - Search & Destroy 1.6.2.46

I recently reinstalled Spybot. It had been compromised somehow. It was using up all this memory, as it still is, and the exe file was not in the Spybot - Search & Destroy directory, so I downloaded the latest version and reinstalled it.

I'm still getting the extreme memory usage.

Can anybody tell me how to make it take less memory? I want to use it as I believe it performs a valuable service.

I thank you in advance for any help you can give.

Spybotnorma
2010-01-30, 12:55
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.

goldenthroat
2010-01-30, 19: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.

Thanks for the explanation. I didn't know that. However, the behavior I was describing is at startup, not after a long period of idleness.

sleze
2010-02-02, 14:36
Is there any way to get access to older versions of Teatimer that don't hog resources (memory and processor) like the current version? The older versions (1.3 I think), only appeared to monitor changes to the registry and that (to me) is the best feature of Teatimer.

sleze
2010-02-02, 16:21
I answered my own question. You can get old versions of spybot at oldversion.com. Using Teatimer from SB 1.3, it uses a whopping 2 MB of memory, monitors the registry and lets Windows 7 monitor the rest.

tooltime63
2010-02-06, 17:48
I have noticed that TeaTimer gradually uses more & more memory until a reboot. After reboot it uses 131MB RAM. I left my PC on for a week & at the end of the week TeaTimer was using just over 1GB of RAM. This appears to indicate a memory leak to me. Anyone else notice the same? I'm running Win 7 Ultimate 64 w/4GB RAM & Dual 3Ghz Intel.

drragostea
2010-02-07, 02:32
For those of you who plan to run resource intensive applications such as Adobe Photoshop, for example, or an anti-virus scan my best advice for you for now is to temporarily disable TeaTimer and then reactivate it after the scan if your resources are limited. I do not know if it is a memory leak. I have encountered this issue before when the 1.6.x build was first released, there was a registry tweak to lower the memory usage but I do not know if it would work.

I would advise against downgrading your TeaTimer. I would much rather have the protection it offers and take the extra step to disable it when it is required rather than strip it of it's protection values for more memory.

Do not worry because the 2.0 build (major upgrade) of Spybot-Search&Destroy will resolve the memory issue.

sleze
2010-03-01, 03:45
I would advise against downgrading your TeaTimer. I would much rather have the protection it offers and take the extra step to disable it when it is required rather than strip it of it's protection values for more memory.

Do not worry because the 2.0 build (major upgrade) of Spybot-Search&Destroy will resolve the memory issue.

For me, TeaTimer's best feature is that it monitors any/all changes to the registry. All its other features are taken care of by the McAfee suite that I am mandated to use by my job. So other than the registry monitor, there are too many duplicate features to justify the processor and memory hog.

IamJim
2010-04-17, 12:58
I have encountered this issue before when the 1.6.x build was first released, there was a registry tweak to lower the memory usage but I do not know if it would work.

Do not worry because the 2.0 build (major upgrade) of Spybot-Search&Destroy will resolve the memory issue.

Don't worry? (laugh) When will 2.0 resolve this...and I would be interested in the regedit for sure..

As for versions? Current...etc...and the past 2-3 upgrades were back in 70me area...sure would love to see the old 30 meg usage...

Last nights download...brought it back way too HIGH for mem usage.

Thx !!

Matt
2010-04-17, 14:32
HI IamJim,



As for versions? Current...etc...and the past 2-3 upgrades were back in 70me area...sure would love to see the old 30 meg usage...

Last nights download...brought it back way too HIGH for mem usage.

If your computer hasn't enough RAM to use TeaTimer, you should disable it.

If you have enough RAM, please stop crying about 70, 100 or perhaps 150 MB.That should be nothing for a new computer with 2, 4 or 8 GB of RAM.

I don't understand your problem... :sad:


When will 2.0 resolve this...Sorry, but I don't know when Team Spybot will release the first public beta version of Spybot 2.0 :)

IamJim
2010-04-17, 14:36
HI IamJim,


If your computer hasn't enough RAM to use TeaTimer, you should disable it.

If you have enough RAM, please stop crying about 70, 100 or perhaps 150 MB.That should be nothing for a new computer with 2, 4 or 8 GB of RAM.

I don't understand your problem... :sad:

Sorry, but I don't know when Team Spybot will release the first public beta version of Spybot 2.0 :)

??? Huh? It's loose code bro...

I'm a programmer from paper tape days..

Adding memory or upgrading? Piss away money not needed?

Get real..

For 1.5 months...it was at an acceptable 70meg usage...after night..popped back up and now at 106

Disable it? Maybe delete it....laugh..

It's been great over the years...I've donated a couple of time also in the past..

Matt?

WRONG ANSWER!!'
Jim:oops:

Matt
2010-04-17, 14:45
??? Huh? It's loose code bro...

I'm a programmer from paper tape days..

Adding memory or upgrading? Piss away money not needed?

Get real..

For 1.5 months...it was at an acceptable 70meg usage...after night..popped back up and now at 106

Disable it? Maybe delete it....laugh..

It's been great over the years...I've donated a couple of time also in the past..

Matt?

WRONG ANSWER!!'
Sorry Jim... it seems that I can't help you. :sad:

I didn't know that 35 MB are so "important"...

IamJim
2010-04-17, 14:53
Sorry Jim... it seems that I can't help you. :sad:

I didn't know that 35 MB are so "important"...

Not a problem Matt, but as mentioned... "Wrong Answer"...lol...as for adding memory...

but this Dell dual Xeon server w/512 runs like a rocket actually...that I have this installed on

I come from a day when a 1meg stick cost US $100.00...so that equates to 3,000.00 just to run TeaTimer at 30meg?

I also used to work for GTE and also Microsoft...and over the years..KNOW that code is bloated and leaks memory...etc..

Keep spending that hard earned $$$ of yours...

Again, thx for the post...but I posted as quite a few others are experiencing HIGH usage also.

Jim