1. OSBot Version: 2.4.75

2. A description of the issue:  Java sat around 380-410MB memory usage up until web walking was used after that the script sat at 660-700MB memory usage, fluctuating here and there of course but never dropping back down to its normal range 380-410MB.  Because this happened in a script of mine I decided to run a test of course and made a test script which attempts to web walk somewhere only once and then just idle once it reach it's destination, the same problem occurred.

3. Are you receiving any errors in the client canvas or the logger? No.

4. How can you replicate the issue? Use the web walker to walk anywhere.

5. Has this issue persisted through multiple versions? If so, how far back? I'm not sure, just noticing this now.

An extra 200-300 MB for web walking is great. If your script doesn't require web walking, then use the regular WalkingEvent. Not sure why everyone is dead set on using web walking to traverse 10 tiles. 

 

 

An extra 200-300 MB for web walking is great. If your script doesn't require web walking, then use the regular WalkingEvent. Not sure why everyone is dead set on using web walking to traverse 10 tiles. 

The issue is not the extra memory whilst the web walker is walking, it's the fact that after it's done walking the memory is not cleared up. I am using the web walker to walk to places like chaos druids in Taverley dungeon from Falador.

The issue is not the extra memory whilst the web walker is walking, it's the fact that after it's done walking the memory is not cleared up. I am using the web walker to walk to places like chaos druids in Taverley dungeon from Falador.

 

That would require re-initializing the web walker every time you call it. A lot of scripts would suffer from this.

Is there something in the web walker that could be causing a memory leak? I've tested my script, Molly's Chaos Druids, quite a bit and have only noticed a huge increase in memory usage after the bot calls the web walker, and sometimes high spikes during usage above 700MB. If I start the script at the chaos druids on a high level account for example, without looting, the bot can stay indefinitely so web walking will never be used. When I do this I notice absolutely no substantial increase in memory, Java will sit around the same memory +/- 5-6MB or so, there is no continual increase in memory over time however, so the issue does not appear to be script related.  I personally have not been able to replicate the OutOfMemoryError that a user of mine is experiencing(you can see his logs here: http://osbot.org/forum/topic/90804-mollys-chaos-druids/page-20), so my only guess at this point is there may be some kind of problem with web walking.

 

I notice my script, and the user who brought this to my attention, are not the only ones experiencing this issue.

http://osbot.org/forum/topic/102879-a-possible-bug-not-entirely-sure/#entry1149594

http://osbot.org/forum/topic/100847-all-premium-scripts-lagg-out-client/

http://osbot.org/forum/topic/102753-scripts-cause-insane-freezing/#entry1148726

Here is an interesting one, you can see in one of snarfboy's logs he gets an OutOfMemoryError right after the script is going to walk, presumably using the web walker :http://osbot.org/forum/topic/79162-%CF%9Dcluehunter-easy-100k-350kh-low-req-all-teleports-mounted-glory-48h-trials/page-54

Error:

[INFO][Bot #2][07/18 12:01:09 AM]: Random solver exited : Welcome Screen
[INFO][Bot #2][07/18 12:01:09 AM]: loop1
[INFO][Bot #2][07/18 12:01:09 AM]: Stamina active: false, status = IDLE
[INFO][Bot #2][07/18 12:01:09 AM]: WALKING TO HAM!!
[INFO][Bot #2][07/18 12:01:09 AM]: WALKING TO [x=3179, y=9630, z=0]
[ERROR][Bot #2][07/18 12:01:30 AM]: Error in bot executor!
java.lang.OutOfMemoryError: Java heap space
    at org.osbot.Cb.<init>(vo:2)
    at org.osbot.lpT8.<clinit>(bg:209)
    at org.osbot.Ec.IiiIiiiIiiiI(dl:150)
    at org.osbot.Ec.IiiIiiiIiiiI(dl:164)
    at org.osbot.jb.IIIiiiiIiIiI(yf:158)
    at org.osbot.rs07.event.WebWalkEvent.execute(fk:151)
    at org.osbot.rs07.event.EventExecutor$2.run(zm:13)
    at org.osbot.rs07.event.EventExecutor.execute(zm:174)
    at org.osbot.rs07.script.MethodProvider.execute(yl:356)
    at org.flamezzz.a.c.NuL.D(rb:846)
    at org.flamezzz.fClueHunter.onLoop(ub:690)
    at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(kn:194)

    at java.lang.Thread.run(Unknown Source)

 

All those topics seem to be about the exact same issue, with multiple users mentioning the same thing. All those scripts in question would be using web walking often.

Edited July 19, 20169 yr by Molly

Web walking is very heavy, I think we anticipate up to 2GB (obviously on the very safe side). That's why when people suggest to "just use webwalking" for every situation, I get pretty upset because the regular WalkingEvent is great for short to medium distances without the resource hit. 

 

For your chaos druid script, make sure you're only using it to walk to/from the bank. While you do that, I'll check my end.