SRL Archive - Bugs

Memory usage?

n3ss3s

2012-01-09 21:36:49

Ok, I put together this -


program new;
var
  TPA: TPointArray;
begin
  repeat
    FindColorsTolerance(TPA, 16777215, 0, 0, 1000, 1000, 20);
    // SetLength(TPA, 0);
    wait(50);
  until(false);
end.

An individual script run seems to use up a maximum of 30 megs of memory and then keeps hovering around that number, but each script run is able to accomplish this? E.g when I run this "script", memory will climb up by 30mb. However, when I stop and restart the script, it'll use another 30mb… Is there a way you guys could eliminate this? (Ok, I'm willing to close my Simba every 50 script runs but I'm guessing this is something that should be taken care of)

eXoTiK

2012-01-09 21:44:53

Even so, 30MB is such a minimal amount to even care about. The average computer comes with 2-4 GB of RAM, so 30MB is not an issue.

n3ss3s

2012-01-09 21:50:53

From: eXoTiK
Even so, 30MB is such a minimal amount to even care about. The average computer comes with 2-4 GB of RAM, so 30MB is not an issue.


If you read the post you'd know that it uses up another 30MB on each script run… Meaning if you're testing something and end up running it a 100 times in 10 minutes you have a problem…

Brandon

2012-01-09 21:54:08

From: eXoTiK
Even so, 30MB is such a minimal amount to even care about. The average computer comes with 2-4 GB of RAM, so 30MB is not an issue.


Ohhh but on the contrary.. I've been testing autocolour functions manually using FindColorsSpiralTolerance..

After a ton of tries.. I got "Out of Memory" error.. and had to restart simba.. after a restart, everything was fine. Actually happened 2 days ago though.

Dgby714

2012-01-09 22:22:50

I can't get this to happen for me? I'm using a Simba without Lape and Extensions.
Would you care to see if that's were this memory leak is coming from?

'Toxin

2012-01-09 23:02:09

I tried running it, checked the simba process in task manager, still was running fine and not spiking ram usage at all. This is odd.

n3ss3s

2012-01-10 15:20:07

Both Lape / PS do this (no extensions), Simba initially is using 15MB, running the script puts it to 49 where it alters between 56 and 49…

Sabzi

2012-01-10 15:26:52

I have tried this as well. PS, extensions; after every stop memory goes back to "default".

Windows 7 64 bit.

EDIT: With Lape however I get this too. But it doesn't stops the script it just hangs it, then I have to terminate it. Memory is not freed up. Maybe I should just wait more till the script finishes peacefully in Lape? I don't think it should take that long tho.

Gu3st...

2012-01-10 15:27:28

When my Simba is idle it uses ~16MB of memory it goes up to ~50MB, and when I stop the script it goes back to ~16MB again

senrath

2012-01-10 15:48:12

Just tested. Mine acts like Sabzi's does, pretty much exactly.

Dgby714

2012-01-10 15:52:07

From: n3ss3s
Both Lape / PS do this (no extensions), Simba initially is using 15MB, running the script puts it to 49 where it alters between 56 and 49…


I meant my Simba doesn't have the extensions engine or Lape at all.
Lape does have quite a few mem leaks.

Dgby714

2012-01-10 15:57:10

From: Sabzi
I have tried this as well. PS, extensions; after every stop memory goes back to "default".

Windows 7 64 bit.

EDIT: With Lape however I get this too. But it doesn't stops the script it just hangs it, then I have to terminate it. Memory is not freed up. Maybe I should just wait more till the script finishes peacefully in Lape? I don't think it should take that long tho.


Currently we cannot stop Lape (Ether the functionality is missing, or we haven't implemented it yet.), You have to terminate the thread.