Hello, I've been experiencing this problem for a while now, but it seems to be getting more and more frequent. When I leave the bot running for a couple hours or overnight or whatever I almost always come back to see my bot gone, it isn't stopped or logged out or anything, it's closed. And most of the times when I leave it overnight it runs for not even an hour before it shuts down.

 

Is this happening to other people? Is there a fix? Because I'm currently leaving my computer on for 8 hours a night to bot 1 hour and spend 7 hours of electricity.

 

Thanks in advance to everyone who cares to help

 

edit: nevermind I just found out that this is a "unsolveable" issue and happens to everyone on osbot i guess.

Edited March 24, 201412 yr by RasTafari

This is happening to me as well.

 

Anyone know of a fix to it? Can't be botting nightmare zone and having this thing crash on me every 30 minutes...

This is happening to me as well.

 

Anyone know of a fix to it? Can't be botting nightmare zone and having this thing crash on me every 30 minutes...

 

From what I understand this is an issue that will only be solved when Osbot 2 comes out

This happenends when your account randomly logs out.

Before starting your bot you should relog, this helped me and works for me.

This happenends when your account randomly logs out.

Before starting your bot you should relog, this helped me and works for me.

 

It seems like an odd fix but I'll try that, thanks!

I'm having the same problems,I'm fairly sure it isn't the account logging out mostly because not 3-4 days ago I was botting for 30-40 hours. And those sessions would only stop due to internet connectivity issues or runescape client updates. I've got no clue why is happening, but after about 20 minutes of running, I instantly log out (of the game, not the client) and the bot re-logs promptly. Then after about another 30 minutes the client just closes. I'm assuming its crashing because it happens in the same time intervals on each occasion.

It's the memory leak, currently there are no known solutions

It's the memory leak, currently there are no known solutions

 

Does this happen with everyone no matter what your RAM/CPU usage is?