I'm not sure what's causing this, and haven't yet seen a solution, but I know last time I made a thread explaining that my client will randomly crash and almost never lasts longer than 2 hours, a lot of people said they had the same problem, and we never found a fix.

 

This problem seems to come and go. It doesn't matter if I use an older version or the latest version, when it's happening, it's happening. What I mean by that is that sometimes I'll go weeks without it happening at all. My client will run all day with no problems for days/weeks on end. Then, I'll get the problem where it randomly crashes, and it does so consistently, rendering the client almost completely useless if I have to babysit it.

 

I'm not an expert and I won't pretend to be like a lot of people do, but a theory I had was that Jagex has something up their sleeves, possibly similar to the alt code character glitch we saw a few years back that people used to disconnect others. Is it possible that they have something (it could very well be an invisible npc or object) that crashes our client? I would assume Orion and any other client but the official RS client would have this problem as well, but I don't know, it's just a theory.

I'm not sure what's causing this, and haven't yet seen a solution, but I know last time I made a thread explaining that my client will randomly crash and almost never lasts longer than 2 hours, a lot of people said they had the same problem, and we never found a fix.

 

This problem seems to come and go. It doesn't matter if I use an older version or the latest version, when it's happening, it's happening. What I mean by that is that sometimes I'll go weeks without it happening at all. My client will run all day with no problems for days/weeks on end. Then, I'll get the problem where it randomly crashes, and it does so consistently, rendering the client almost completely useless if I have to babysit it.

 

I'm not an expert and I won't pretend to be like a lot of people do, but a theory I had was that Jagex has something up their sleeves, possibly similar to the alt code character glitch we saw a few years back that people used to disconnect others. Is it possible that they have something (it could very well be an invisible npc or object) that crashes our client? I would assume Orion and any other client but the official RS client would have this problem as well, but I don't know, it's just a theory.

Lots of people having this issue, previously myself included. I think I found the solution. At least it has solved the problem for me so far(going on 5 days no crash running 8 hrs a day). I used to have it happen randomly for me sometimes in less than 5 minutes of running, sometimes i get a few hrs. Would happen on average 3-4 times per day. My solution was to allocate more ram to the osbot client. It has "so far" fixed the problem for me. As many know, osbot currently is in beta, it also has massive memory and cpu leaks. What this means is that the java machine will use more and more ram/cpu to continue running the program. Sometimes it uses so much that the java machine closes the java application. By default java doesnt use that much ram for its applications. I have currently set my java for the osbot client to use 4 gigabytes of ram and have not seen this closing problem since. You should try this fix. If you need help trying this, feel free to pm me or better yet,

post here: http://osbot.org/forum/topic/29790-briareos2285s-tech-support-service/

 

I would be happy to assist you in troubleshooting/diagnosing your problem to the best of my ability. No charge either!

Thanks for the help, I allocated 4gb of ram to Java as well since I have 8gb and I don't run anything else other than a browser. Hopefully that does the trick. I'll let ya know!

cool. Just curious. What was your method to allocate the ram? There are multiple ways of doing it.

I changed the Java runtime parameters to -Xmx4096m

 

I have 8gb of ram so I figured I'd go with 4 as well since that also worked for you.

 

I had it crash on me again, but it did last a good 4 or 5 hours this time.

Edited December 26, 201312 yr by breezin36

I would undo what you did, and instead trying running osbot with a batch file so it has command line. You only changed the xmx, this will change it for the xms too.... Add this: 

 

java -jar -Xmx4096M -Xms4096M osbot.jar

pause

 

I originally did it the same way you did, and it only slightly improved it. I did what I listed above and 9 times out of 10 my bot runs for 10 hrs+ before I close it myself or unless it gets stuck in a random or runs out of supplies.

Edited December 27, 201312 yr by briareos2285

If you're still recieving these Errors/Bugs please PM me or another staff member.