When im botting for a good few hours , the osbot client will close itself? is it just me or anyone else have the same problem?

This can be a number of issues:

 

1) Your client can close due to a leak in your CPU/Memory thus causing your computer to overload and force close the client.

 

2) Your connection is having difficulties connecting to the server in which you leave your PC, get logged out and then after 5 minutes the client auto shuts down if you are not logged in.

 

3) Your connection is having difficulties stabilizing and continues to disconnect/connect to the server, in which you go online/offline constantly, after a certain period of these events, the client automatically closes.

 

4) The server itself is having trouble stabilising and is either under a DDoS attack in which you cannot connect to the server and the above happens.

 

Hopefully this helps.

 

thanks gilgad , how do i check against #1?

Close down excess programs such as skype, steam, your web browser.

 

Right click your task bar, open your task manager, click on process, find the java.exe*32 and right click, set priority high.

 

If it still closes then you need to clean out your computer and check for virus's/malware.

 

If it still closes, then you just need a better computer xD

 

This can be a number of issues:

 

1) Your client can close due to a leak in your CPU/Memory thus causing your computer to overload and force close the client.

 

2) Your connection is having difficulties connecting to the server in which you leave your PC, get logged out and then after 5 minutes the client auto shuts down if you are not logged in.

 

3) Your connection is having difficulties stabilizing and continues to disconnect/connect to the server, in which you go online/offline constantly, after a certain period of these events, the client automatically closes.

 

4) The server itself is having trouble stabilising and is either under a DDoS attack in which you cannot connect to the server and the above happens.

 

Hopefully this helps.

 

 

#1 Speaking from using 3 different 4 cores, when it overheats rapidly it shuts down the power if its anywhere near modern, never had this happen with osbot. If its a slow onset, the osbot client freezes first, then the entire os freezes. No automatic shutdown of osbot. My overloads have always come from cpu maxout though, never ram (i keep it below 70%max at all times).

I guess this could be dependent on your specific cpu/mem/mobo/os though, how it handles it, but none of the cpus that i have used have the ability to distinguish wich application that is making the system unstable and auto shut it down.

 

#2 i can say from experience this is false statement. OSbot does not auto shut down after 5 min if not logged in. Regardless if you mean logged in to game or to osbot account.The shutdown he is refering to is instant aswell, even if you run multiple copies, they all vanish at the exact same moment (seen this myself in action), logged in or not.

 

#3 doesnt sound likely either, definitely not as singular reason. During the bad server issues some weeks ago when everyone was DCing/reconnecting like 10 times per hour (add in breaks to that), there were no automatic shutdown of the client for me. Maybe its like this, but in that case if you actually KNOW this, just tell us the limit of logins/outs per minute before automatic shutdown, otherwise just sound like ur guessing this one.

 

#4 this i dont know about, but i dont think jagex servers suffers from lack of DDoS protection, wouldnt angry botters be ddosing them left and right otherwise? Also, when a serve goes offline and your bot is disconnected and tries to reconnect to an offline server, it doesnt cause automatic shut down of the client itself, saw this during the recent jage server probs.

 

I also had big problems with this, as i see it, bug, some time ago. I asked but noone really knew the cause and there were some others who experienced the same. I have no idea what solved it. I dont remember if it was a new osbot version, but i do remember that it both happened and not happened on unchanged pc setup. So no hardware or opsys change/update. 

 

I do not have this problem now.

Edited January 10, 201412 yr by notimportant1

As mentioned, I would aim towards it being an issue with your CPU.

Seeing as it happens randomly.

What are your specs? 

#1 Speaking from using 3 different 4 cores, when it overheats rapidly it shuts down the power if its anywhere near modern, never had this happen with osbot. If its a slow onset, the osbot client freezes first, then the entire os freezes. No automatic shutdown of osbot. My overloads have always come from cpu maxout though, never ram (i keep it below 70%max at all times).

I guess this could be dependent on your specific cpu/mem/mobo/os though, how it handles it, but none of the cpus that i have used have the ability to distinguish wich application that is making the system unstable and auto shut it down.

 

#2 i can say from experience this is false statement. OSbot does not auto shut down after 5 min if not logged in. Regardless if you mean logged in to game or to osbot account.The shutdown he is refering to is instant aswell, even if you run multiple copies, they all vanish at the exact same moment (seen this myself in action), logged in or not.

 

#3 doesnt sound likely either, definitely not as singular reason. During the bad server issues some weeks ago when everyone was DCing/reconnecting like 10 times per hour (add in breaks to that), there were no automatic shutdown of the client for me. Maybe its like this, but in that case if you actually KNOW this, just tell us the limit of logins/outs per minute before automatic shutdown, otherwise just sound like ur guessing this one.

 

#4 this i dont know about, but i dont think jagex servers suffers from lack of DDoS protection, wouldnt angry botters be ddosing them left and right otherwise? Also, when a serve goes offline and your bot is disconnected and tries to reconnect to an offline server, it doesnt cause automatic shut down of the client itself, saw this during the recent jage server probs.

 

I also had big problems with this, as i see it, bug, some time ago. I asked but noone really knew the cause and there were some others who experienced the same. I have no idea what solved it. I dont remember if it was a new osbot version, but i do remember that it both happened and not happened on unchanged pc setup. So no hardware or opsys change/update. 

 

I do not have this problem now.

 

You cant expect me to know the exact amount of log ins/outs, what do you think I am, an osbot developer? All i know is that those are the facts, although the times are probably incorrect, if you know so much about OSBot's development system, why don't you go spread your knowledge upon everyone.

 

The issue for you is #1. And yes, all those statements are correct because the development/mod team have tested each statement and the case that you proved incorrect has actually been the case multiple times. (Even though the OFFLINE state in #2 is semi incorrect, I could develop it further as to make it add on to #1 as the state is it is attempting to connect to the osbot servers 24/7).

You cant expect me to know the exact amount of log ins/outs, what do you think I am, an osbot developer? All i know is that those are the facts, although the times are probably incorrect, if you know so much about OSBot's development system, why don't you go spread your knowledge upon everyone.

 

The issue for you is #1. And yes, all those statements are correct because the development/mod team have tested each statement and the case that you proved incorrect has actually been the case multiple times. (Even though the OFFLINE state in #2 is semi incorrect, I could develop it further as to make it add on to #1 as the state is it is attempting to connect to the osbot servers 24/7).

Well what i wrote is correct because i have observed it. Not making guesses like you with for example the "auto shutdown after x login attempts" theory.

 

Up to reader to choose whom to believe now, not gonna play the "yes, no" game.

And shrooms, go change login info on the osb client to a faulty password then watch it hammer it for half an hour or so and you can see im correct.

 

Btw i only replied to give Shrooms some correct info, im seeing so many people giving "opinions" nowadays on matters wich have factual answers. If you dont know, just say so or nothing at all, only confusing otherwise.

 

Didnt reply for your sake, only for him, and im ending my input here because you are rude and incorrect and i dont want to argue with a global mod. Good job silencing someone who wants to help on a matter who he has actual experience with.

 

Shrooms if u want to ask my input u can pm me.

Edited January 13, 201412 yr by notimportant1

Well what i wrote is correct because i have observed it. Not making guesses like you with for example the "auto shutdown after x login attempts" theory.

 

Up to reader to choose whom to believe now, not gonna play the "yes, no" game.

And shrooms, go change login info on the osb client to a faulty password then watch it hammer it for half an hour or so and you can see im correct.

 

Btw i only replied to give Shrooms some correct info, im seeing so many people giving "opinions" nowadays on matters wich have factual answers. If you dont know, just say so or nothing at all, only confusing otherwise.

 

Didnt reply for your sake, only for him, and im ending my input here because you are rude and incorrect and i dont want to argue with a global mod. Good job silencing someone who wants to help on a matter who he has actual experience with.

 

Shrooms if u want to ask my input u can pm me.

 

You seem very ignorant to the fact that there are also a few .. Thousand.. other.. people who have "Observed" the client closing down as well

 

Observing is one thing, knowing is another, releasing info is another thing as well.

 

Fairly sure I have "Observed" the client more then you have, and i'm also fairly sure that I have more inside information on the client then you have as well.. from the client developers.

 

Anyhow, if you want to discuss your information with anyone, feel free to make a post regarding the client and the exact reasoning/s behind the coding and/or the event of the client closing, or feel free to PM anyone about it.