SRL Archive - Bugs

I have posted this before, it hasn't been fixed, and you guys may need a reminder, after a long stint with simba open, I get access violations every time I try and do something which would normally create a popup window (kidna) eg. Open, Save (if the document has been saved before its fine) and a couple of other things. Its a pain in the arse and needs to be fixed.

Since once it wouldn't shut down, I opened up task manager, and noticed it was using 250,000 whateverucallems of RAM, when it normally uses 10% of that. I am about to test to see if it will happen even if I leave a blank script open, and nothing happening, I haven't seen any correlation between scripts running and this failing, however.

bugs.villavu.com?

That kind of stuff happens to me as well when i run simba for a while(especially when i run a few different scripts one after another). It also look to me that there are memory leaks, because if you just open up simba it doesn't take a lot of RAM, but once you start and stop a script, the RAM consumption increases to like 270,000k and stays like that until its restarted, even though its doing nothing.

From: kongking
That kind of stuff happens to me as well when i run simba for a while(especially when i run a few different scripts one after another). It also look to me that there are memory leaks, because if you just open up simba it doesn't take a lot of RAM, but once you start and stop a script, the RAM consumption increases to like 270,000k and stays like that until its restarted, even though its doing nothing.

I agree with the memory leaks.
I restart Simba everytime I run a script otherwise it gets unbearable after a couple of runs.

Bad Boy JH: In your simba settings check "Settings->Scripts->Path".
Make sure that directory is there.

My Simbas never go over 50000K. (Take into account I don't use SRL)

Do you use smart?

I left it there, with no script, did nothing…basically I opened it, before I went shopping, When I got back, I hit CTRL+O and I got an access violation, perhaps its an memory leek in the extentions.

From: kongking
That kind of stuff happens to me as well when i run simba for a while(especially when i run a few different scripts one after another). It also look to me that there are memory leaks, because if you just open up simba it doesn't take a lot of RAM, but once you start and stop a script, the RAM consumption increases to like 270,000k and stays like that until its restarted, even though its doing nothing.

That's just SMART/Runescape running.

I assume you're using 750? Does the debug say anything?

From: Wizzup?
That's just SMART/Runescape running.

I assume you're using 750? Does the debug say anything?

Simba still takes about 270,000k of ram even if its not doing anything, and smart is closed(its basically the same as if it were just started up, doesn't do anything, but still uses a lot of RAM). Yes, Im using version 750, and nope the debug doesn't say anything.

=/ My Simba idles at 20,000K when started up (After fonts load and everything)

From: kongking
Simba still takes about 270,000k of ram even if its not doing anything, and smart is closed(its basically the same as if it were just started up, doesn't do anything, but still uses a lot of RAM). Yes, Im using version 750, and nope the debug doesn't say anything.

Yes it will still use 270,000k RAM if you aren't doing anything - that's part of the point of RAM!

You store stuff in your RAM so it can be accessed fast. Runescape takes up a fair bit of memory, so when you start SMART you will see memory usage for Simba increase dramatically. If you want to free up Simba's memory that is for Runescape, you will have to close Simba. (Just tested closing just SMART, and it seems that closing just SMART won't free up the RAM - might be a bug, might be a feature so when you rerun your script SMART starts up faster)

I just wanted to point out that CPU cycles do not require RAM, so just because Simba isn't doing anything doesn't mean it shouldn't be using any RAM. If that were the case a freshly opened Simba would take up virtually nothing.

Besides .. is it really that much of a trouble to start up Simba again?

It's just that the SMART plugin is not unloaded and Java GC doesn't free the memory… (yet, anyway) If you start SMART again it won't use another 250MB. Ask Benland, he knows more about the Java JVM than I do.

EDIT: Bad Boy, can you keep the debug console open and make a screenshot of it when the access violation occurs?

From: Capricorn
Yes it will still use 270,000k RAM if you aren't doing anything - that's part of the point of RAM!

You store stuff in your RAM so it can be accessed fast. Runescape takes up a fair bit of memory, so when you start SMART you will see memory usage for Simba increase dramatically. If you want to free up Simba's memory that is for Runescape, you will have to close Simba. (Just tested closing just SMART, and it seems that closing just SMART won't free up the RAM - might be a bug, might be a feature so when you rerun your script SMART starts up faster)

I just wanted to point out that CPU cycles do not require RAM, so just because Simba isn't doing anything doesn't mean it shouldn't be using any RAM. If that were the case a freshly opened Simba would take up virtually nothing.

Besides .. is it really that much of a trouble to start up Simba again?

No, smart doesn't run any faster, on the contrary it becomes unstable sometimes, and I don't see the logic in the some process taking ram when its not doing anything, when it could be used for the other programs i use, so obviously when simba doesn't do anything it shouldn't take any ram.(thats like getting paid for doing nothing, it just doesn't work that way :p)

From: Wizzup?
It's just that the SMART plugin is not unloaded and Java GC doesn't free the memory… (yet, anyway) If you start SMART again it won't use another 250MB. Ask Benland, he knows more about the Java JVM than I do.

Yep, it doesn't take another 250megs again, but i just wanted to know if it was a bug or not.

From: kongking
No, smart doesn't run any faster, on the contrary it becomes unstable sometimes, and I don't see the logic in the some process taking ram when its not doing anything, when it could be used for the other programs i use, so obviously when simba doesn't do anything it shouldn't take any ram.(thats like getting paid for doing nothing, it just doesn't work that way :p)

Simba doesn't unload SMART if a script is stopped because that way SMART won't have to be loaded every time you run a script. Simba does not know when you close SMART using the GUI, so therefore cannot unload the dll if you do so. :)

From: Wizzup?
Simba doesn't unload SMART if a script is stopped because that way SMART won't have to be loaded every time you run a script. Simba does not know when you close SMART using the GUI, so therefore cannot unload the dll if you do so. :)

When i stop a script, i usually close smart as well. So is there a way to tell simba that ive closed smart?

From: kongking
When i stop a script, i usually close smart as well. So is there a way to tell simba that ive closed smart?

Can try yelling at your computer, but probably won't make a difference

From: kongking
When i stop a script, i usually close smart as well. So is there a way to tell simba that ive closed smart?

No, you but you could try and ask Benland to make SMART free it's Java stuff if the GUI is closed. :)

From: mastaraymond
Can try yelling at your computer, but probably won't make a difference

lol'd hard at this.