100% CPU Usage every time I start a script

[Retweets]

I've been getting 100% CPU Usage since the newest OSBot update.. I have quite a good PC, and was able to run 3-4 bots before the update.

The script that I literally can't use rn is Stealth Quester, could be because of webwalking. The client just freezes up to the point that I have to close it. Can anyone help me out, because I can't bot at all right now.

[Token]

I've noticed the same issues while webwalking after the last client update (or the 2 webwalking updates before it), the problem you are describing is a GC overhead limit exceeded error thrown during webwalking events (out of memory error) with the exact same code as before the updates. The PC you are running OSBot on doesn't have that much importance because we are talking about a resource management error in this case which will always result in a JVM crash.

[Retweets]

2 minutes ago, Token said:

I've noticed the same issues while webwalking after the last client update (or the 2 webwalking updates before it), the problem you are describing is a GC overhead limit exceeded error thrown during webwalking events (out of memory error) with the exact same code as before the updates. The PC you are running OSBot on doesn't have that much importance because we are talking about a resource management error in this case which will always result in a JVM crash.

Although most of what you said was chinese to me, do you know any way I can fix it myself. Or are we looking at something the client will need a fix for?

[Token]

11 minutes ago, Retweets said:

Although most of what you said was chinese to me, do you know any way I can fix it myself. Or are we looking at something the client will need a fix for?

On your end all you can do is start a new client every time you start a script and remove all unnecessary local scripts you have in your scripts folder, your best bet would be writing a detailed bug report in the client bugs & suggestion section with all information about your operating system

 

EDIT: also try starting with -mem 1024 flag from CLI

Edited February 26, 2017 by Token

[darol]

1 hour ago, Retweets said:

I've been getting 100% CPU Usage since the newest OSBot update.. I have quite a good PC, and was able to run 3-4 bots before the update.

The script that I literally can't use rn is Stealth Quester, could be because of webwalking. The client just freezes up to the point that I have to close it. Can anyone help me out, because I can't bot at all right now.

If you are running 2 scripts on 1 client and them both are using web-walking, your cpu rockets to 100% because  it cannot handle it, 2scripts on 1client is only fine if you're like training fletching at bank or something and the script doesn't require web-walking.  Check  out the latest threads before posting  yours there's really alot of info around here.

[Retweets]

2 hours ago, darol said:

If you are running 2 scripts on 1 client and them both are using web-walking, your cpu rockets to 100% because  it cannot handle it, 2scripts on 1client is only fine if you're like training fletching at bank or something and the script doesn't require web-walking.  Check  out the latest threads before posting  yours there's really alot of info around here.

I am running one script on one client, no other clients active and it's still doing it bro. I read all posts about this, but nothing gave a solution.

2 hours ago, Token said:

On your end all you can do is start a new client every time you start a script and remove all unnecessary local scripts you have in your scripts folder, your best bet would be writing a detailed bug report in the client bugs & suggestion section with all information about your operating system

 

EDIT: also try starting with -mem 1024 flag from CLI

How do you start with -men 1024 flag from CLI?

[Token]

Just now, Retweets said:

I am running one script on one client, no other clients active and it's still doing it bro. I read all posts about this, but nothing gave a solution.

How do you start with -men 1024 flag from CLI?

There are tutorials on using the CLI on the forums, the combination of -Xms256m with -mem 1024 should prevent any out of memory errors (do not use -Xmx1024m as the client overrides that flag)

[Anne]

@Alek @Zach @MGI

[Basedgoy]

I'm having the same issue with the same script. Shame cause otherwise it's wonderful