Or are my specs just bad?

I3 -2120 processor , 6850 radeon hd 1gb graphics card, 4gb ram

 

Only running 1 bot. and my computer is really slow

Edited March 7, 201412 yr by Hydro

Or are my specs just bad?

I3 -2120 processor , 6850 radeon hd 1gb graphics card, 4gb ram

 

Only running 1 bot. and my computer is really slow

Yeah it's poor coding. And by poor I mean, I couldn't do any better myself, but if this was a professional company they would have. Not sure if it's as much memory leak as it's just inefficient programming though.

(I mean, I can run most games without hassle, but osbot is as tough on my computer as even borderlands 2)

Edited March 7, 201412 yr by Prayanthem

Try ending the java process tree and open it back up. Most of the time I find if i open 2-3 tabs or clients and then exit them all out by one it stays really high.

Let me know if you want the text to make a .bat file which will kill the client if the memory usage exceeds a select amount.

Like, okay. Say you make a boolean, right? That means 0 or 1. But then you get into programming, aka scripting, and that 0 or 1 takes up O(logn) of bytes. Basically, just make sure that after you use your booleans, you release their memory by setting them = somewhat. If you keep the computer guessing, it'll never really know how much memory to allocate, and then obviously you never leak anything. I'm a Computer Scientist so trust me.

Like, okay. Say you make a boolean, right? That means 0 or 1. But then you get into programming, aka scripting, and that 0 or 1 takes up O(logn) of bytes. Basically, just make sure that after you use your booleans, you release their memory by setting them = somewhat. If you keep the computer guessing, it'll never really know how much memory to allocate, and then obviously you never leak anything. I'm a Computer Scientist so trust me.

Obvious troll is obvious. If not:

 

Hey! I am a computer science student, and I would just like to clarify that booleans take up n-bits not O(logn)! Also, what you are saying doesn't make sense at all! They are always set to some value, most languages on initialisation just leave whatever is at that memory address, so it could be 0 or 1 depending on what garbage is in memory. If you are looking for a leak, and looking at booleans, you are doing something wrong.

 

Also... programming is not equivalient to scripting :C

Edited March 8, 201412 yr by Prayanthem

Obvious troll is obvious. If not:

 

Hey! I am a computer science student, and I would just like to clarify that booleans take up n-bits not O(logn)! Also, what you are saying doesn't make sense at all! They are always set to some value, most languages on initialisation just leave whatever is at that memory address, so it could be 0 or 1 depending on what garbage is in memory. If you are looking for a leak, and looking at booleans, you are doing something wrong.

 

Also... programming is not equivalient to scripting :C

 

I'm also a CS student and I was totally being a troll.

 

after you use your booleans, you release their memory by setting them = somewhat. If you keep the computer guessing, it'll never really know how much memory to allocate

 

Thought that was the giveaway. 

Edited March 8, 201412 yr by TheSaint