Possible Memory Leak
- Thread starter mhieta
- Start date
mhieta,
When the Spybot program is closed (after exit) that item shouldn't be there at all and I don't have that problem on any of my computers. Perhaps it is the version you are running or the operating system you use or some interaction with other software. Without any real information it's not possible to even guess.
When the Spybot program is closed (after exit) that item shouldn't be there at all and I don't have that problem on any of my computers. Perhaps it is the version you are running or the operating system you use or some interaction with other software. Without any real information it's not possible to even guess.
Hi Greyfox,
Thanks for your answer. I'm using 1.6.0.30 version.
Please try these steps..
1. Click Check for problems
2. After 4000 items checked click Stop check
3. Repeat 1&2 several times
4. Check SpybotSD.exe Mem Usage and compare Mem Usage when you first started Spybot.
You can see that the memory usage is pretty high, yes its released after Exit. But still it should not "keep memory itself" if someone wants to scan several times (don't know why but still...). Also this same thing happens if you Check for problems and let it run and check all items and then Check for problems again.
- Marko
Thanks for your answer. I'm using 1.6.0.30 version.
Please try these steps..
1. Click Check for problems
2. After 4000 items checked click Stop check
3. Repeat 1&2 several times
4. Check SpybotSD.exe Mem Usage and compare Mem Usage when you first started Spybot.
You can see that the memory usage is pretty high, yes its released after Exit. But still it should not "keep memory itself" if someone wants to scan several times (don't know why but still...). Also this same thing happens if you Check for problems and let it run and check all items and then Check for problems again.
- Marko
Marko,
OK, I see what you mean. Using version 1.6.1.38
Program opened: Mem 33,364K
First stop: Mem 75,876K
Second stop: Mem 125,768K
Third stop: Mem 176,016K
I must say that this is not something I would normally do - I don't start a scan unless I have the time to let it complete, and it does clear the memory on exit so it will probably not adversely affect a large number of users, however you are right, when the scan is stopped it is terminated, so the memory should be cleared and it should not accumulate.
This is perhaps worth referring to the "bugs and features request" forum.
That area has the following heading
Proper Forum?
Ask who to add it to the tracker?
Unfortunately I don't know, perhaps some one else can explain exactly how to do this.
OK, I see what you mean. Using version 1.6.1.38
Program opened: Mem 33,364K
First stop: Mem 75,876K
Second stop: Mem 125,768K
Third stop: Mem 176,016K
I must say that this is not something I would normally do - I don't start a scan unless I have the time to let it complete, and it does clear the memory on exit so it will probably not adversely affect a large number of users, however you are right, when the scan is stopped it is terminated, so the memory should be cleared and it should not accumulate.
This is perhaps worth referring to the "bugs and features request" forum.
That area has the following heading
Proper Forum?
Ask who to add it to the tracker?
Unfortunately I don't know, perhaps some one else can explain exactly how to do this.
Hi Greyfox,
Just tested and this memory leak issue also applies to these versions:
1.6.1.41
1.5.2.20
1.4
And maybe other versions as well.
About that bug tracker place. I have tried that, posting new issue. But then I only get:
mhieta, you do not have permission to access this page. This could be due to one of several reasons...
So maybe someone who cans can move this thread to right place
- Marko
Just tested and this memory leak issue also applies to these versions:
1.6.1.41
1.5.2.20
1.4
And maybe other versions as well.
About that bug tracker place. I have tried that, posting new issue. But then I only get:
mhieta, you do not have permission to access this page. This could be due to one of several reasons...
So maybe someone who cans can move this thread to right place
- Marko
There were too many support questions and incomplete reports, so we disabled direct reporting there. I must admit the "proper" should've been better defined though
Will move this thread to the beta forum (not because this is a beta issue, but because I tend to deal with bugs there). Feel free to post a suggested bugtracker entry here and I'll add it
Hi PepiMK,
Thanks..
Okay, post this in to bug tracker:
---
Please try these steps..
1. Click Check for problems
2. After 4000 items checked click Stop check
3. Repeat 1&2 several times
4. Check SpybotSD.exe Mem Usage and compare Mem Usage when you first started Spybot.
This memory leak issue applies to these versions:
1.6.1.41
1.6.0.30
1.5.2.20
1.4
You can see that the memory usage is pretty high, yes its released after Exit. But still it should not "keep memory itself" if someone wants to scan several times (don't know why but still...). Also this same thing happens if you Check for problems and let it run and check all items and then Check for problems again.
---
- Marko
Thanks..
Okay, post this in to bug tracker:
---
Please try these steps..
1. Click Check for problems
2. After 4000 items checked click Stop check
3. Repeat 1&2 several times
4. Check SpybotSD.exe Mem Usage and compare Mem Usage when you first started Spybot.
This memory leak issue applies to these versions:
1.6.1.41
1.6.0.30
1.5.2.20
1.4
You can see that the memory usage is pretty high, yes its released after Exit. But still it should not "keep memory itself" if someone wants to scan several times (don't know why but still...). Also this same thing happens if you Check for problems and let it run and check all items and then Check for problems again.
---
- Marko
Well, in a way that is exactly why the bugtracker is closed - a look at the bugtracker should show that I'm very paranoid about a proper Situation/Experienced/Expected structure, see this explanation
Still, the steps to reproduce were the most important thing here, and they are well described I first thought this might be just the cache, but that numbers are summing up shows that its more than that.
It does no longer appear in 2.0, I'll see if I can backport the changes before releasing the final 1.6.1
Still, the steps to reproduce were the most important thing here, and they are well described
I first thought this might be just the cache, but that numbers are summing up shows that its more than that.It does no longer appear in 2.0, I'll see if I can backport the changes before releasing the final 1.6.1
Memory usage of what? Spybot-S&D while scanning? Through repeted stops like described by mhieta, or with a single scan? Or TeaTimer.exe?