Molly

Not sure honestly, been quite awhile since I have consistently used this script. When I wrote it I used it to level up an alt and didn't have issues. 48 trial given, sorry for the delay.

Hey guys, sorry for delayed responses and I'm not sure if trials went out to everyone as my account was compromised. Please let me know if you received your trials and were able to use them!

Sorry for the delayed response, I'll write this down and should be able to get to it later tonight for you.

No, unfortunately I cannot. As this is an issue not being caused by any kind of problem with my script I would rather not begin writing an extensive work around if the issue may be addressed in the coming days. Other users are reporting the same issue you are experiencing with multiple other scripts. That, and I don't have much free time these next couple of days to program as I am busy IRL. Right now I am trying to optimize the script a bit to prevent any sort of spikes that may push the memory usage over the edge. That being said, if the issue is not with my script but rather an overlying problem the problem will likely persist. Edit: So far I haven't had any luck reducing memory usage of the script, the script doesn't use any significant amount of memory until web walking is called. Pushing an update for a work around for Taverly druids right now, it will be a checkbox on the GUI called Low Memory Walking.

quest cape, fire cape, full void /w all helms, d def.

Judging by the posts in the bug section this is not something related to my script, other user's are experiencing this with other scripts as well and have reported the issue. I wish there was something I could do about it, but if it's web walking related, there is not. If this issue doesn't get addressed soon, or at least acknowledged, I'll write a custom walker for the time being.

I just tried running a test script that simply executes this command once: and then just stands around once it reaches destination, one would think the memory usage would drop back to around my normal of 380-410MB, however it does not, it stays around 660-700MB. The issue appears to be web walking related. I'll be posting a topic to get some input from other scripters and then reporting it as a bug if I am not simply overlooking something. Edit: The CPU usage issue you experience doesn't seem to occur for me, I'll get spikes to 20% sometimes during combat, usually when attempting to loot or search for a new target, perhaps that is something I can remedy, but that would not be causing the memory leak issue. My CPU usage always drops back down as well, it's simply a spike. The 80% usage you see when the client freezes could be caused by the bot continually trying to do something that requires memory, which it does not have available, causing the CPU to spike. That would be my guess at this point.

Okay so what I have found so far is that this somehow seems to be related to walking. If I start the bot at the druids already it will sit there and fight, loot, etc and will hover around 5-7% of my CPU and around 380-410MB of RAM. However, as soon as the bot needs to bank the CPU usage shoots up randomly during walking, it does fall back down for me, what does not come back down is the amount of RAM being used, it stays between 660-700MB even after walking has finished. I'm trying to see what I can do about this, for walking I simply use the web walker, I'm not sure exactly why all the memory it apparently uses stays being used after it finishes walking. Edit: I also found other uses describing a similar problem, one user even indicates it occurs during web walking: http://osbot.org/forum/topic/102753-scripts-cause-insane-freezing/#entry1148726 Edit x2: Also trying a private script of mine that is a simple gathering script, I'm doing this because there is far less code to sort through in the script, actually there is very little. I am experiencing the same issue when the script uses web walking.

Still at work for a bit but I have an idea as to what my be causing an issue, not 100% sure but I'll check it out here soon.

I'll continue to look into after I get off work, what's odd is I have had zero issues running it and no other users are reporting this issue either. If this was a memory leak issue I'd imagine I'd have a plethora of users here complaining about the same problem.

Those logs indicate the bot is not being allocated enough memory. An out of memory error is being thrown by java.

I'll run it some more and see if I can replicate the issue, if you open the logger prior to starting the script and get a chance to screenshot it if it does this again that would be great.

I don't get this issue, what does the logger say? Have you tried running in low cpu mode?

Trials given. Sure, just like the OP whenever you want the trial and it should go out within an hour.

Just gave you a 48hr trial.

Does not currently support that, I can add it though.

Just posting to confirm you all received trials.

Like the OP for trials guys. Post your logger.

You have one now.

Yeah it always drops tea, that setting is for when stealing things like cakes, silk, gems, etc. I have the bot set to bank those things by default. Sure just gave you a trial.

Edgeville and looting bag both work now.

Please link the logger when you have these issues. Post settings etc, there is a bug report form in the OP that outlines how to report a bug, it makes it much easier to fix. Also no, level 10 farmers are not included because as far as I'm aware they are not worth doing.

You guys both have trials now. Also, fixed cake stealing while stealing from other targets and also added bot bringing food in inventory when stealing from wall safes.

Okay, will change that today. Like the OP for trials guys. I will, I'll try to get to it within the next couple days. Will be working on this today. Will be working on this today.

So if it is correctly clicking the object through the wall, whats the issue?