edit this guy confirms my point. so you are still wrong bro sorry.

 so we understand what a memory leak but do you have proof that it is a memory leak  that is in effect before the client closes? basicaly you dont experience this client closing right?

so then you dont experience a memory leak either....  either way you can't realy prove this is from a memory leak can you? and if it is that means nothing. Since osbot always had memory leak problems, It didnt always  randomly close for me, so then this must be a recent issue that is obviously accuring more often even for botters with good specs,

thus my original point that it is pretty much a shittier osbot still stands.

 

Yes, it is program-oriented. It has always been easy to note the memory usage rising the longer you have your bot running, but never to the point where it closes.

 

edit this guy confirms my point. so you are still wrong bro sorry.

 so we understand what a memory leak but do you have proof that it is a memory leak  that is in effect before the client closes? basicaly you dont experience this client closing right?

so then you dont experience a memory leak either....  either way you can't realy prove this is from a memory leak can you? and if it is that means nothing. Since osbot always had memory leak problems, It didnt always  randomly close for me, so then this must be a recent issue that is obviously accuring more often even for botters with good specs,

thus my original point that it is pretty much a shittier osbot still stands.

 

Whatever, I never said it only depends on PC, I said IT IS affected by what PC you have.

To be quite honest, it is obvious that memory leak is appearing, and that's what I've been discussing so far, I've never even started going about any other possible problems OSBot client may be having.

 

Even so, if we went through any possible causes that you suggest, in definite most of cases, your PC would play a role in them. That's exactly why some people are having problems, some do not.

Edited February 9, 201411 yr by Nitrousek

Quite obvious Nitrousek knows what he is on about. Majority of the people complaining about the client closing are people who think their computers are so amazing that they can handle 100 programs open on top of osbot and still expect it not to crash.

 

Almost everyone i've asked have said, yeah i got this amazing computer it can do all these things, like run Lol, live stream ,youtube, WoW, runescape AND OSbot at the same time, my computer isn't the problem, its the client! grrr!!!! *Doesn't realise that OSBot has memory leak and you cant have so many programs open at the same time because is stupid*

 

Whatever, I never said it only depends on PC, I said IT IS affected by what PC you have.

To be quite honest, it is obvious that memory leak is appearing, and that's what I've been discussing so far, I've never even started going about any other possible problems OSBot client may be having.

 

Even so, if we went through any possible causes that you suggest, in definite most of cases, your PC would play a role in them. That's exactly why some people are having problems, some do not.

hmmm, i remember you saying to get a better pc. That would mean a bad pc would have this issue, and a good pc would not.

people with good specs also have this problem, so then it must be osbot.

your'e original response was in osbots defence.

Quite obvious Nitrousek knows what he is on about. Majority of the people complaining about the client closing are people who think their computers are so amazing that they can handle 100 programs open on top of osbot and still expect it not to crash.

 

Almost everyone i've asked have said, yeah i got this amazing computer it can do all these things, like run Lol, live stream ,youtube, WoW, runescape AND OSbot at the same time, my computer isn't the problem, its the client! grrr!!!! *Doesn't realise that OSBot has memory leak and you cant have so many programs open at the same time because is stupid*

 

Are you not realising that the majority of people having this problem are only running their computers in an almost idle state except for one or limited instances of osbot and no other programs because they are afk (i.e. overnight).

 

Don't worry man, just gotta wait till OSB2, only a few years to go!

 

Are you not realising that the majority of people having this problem are only running their computers in an almost idle state except for one or limited instances of osbot and no other programs because they are afk (i.e. overnight).

 

 

Yeah and those people probably haven't restarted their PC to nullify the effect of the memory leak before leaving it on for 10 hours overnight in which all the lost memory from the other programs are still amidst making no difference whether they're open/closed, you've still lost memory, and the memory leak is still in effect.

Quite obvious Nitrousek knows what he is on about. Majority of the people complaining about the client closing are people who think their computers are so amazing that they can handle 100 programs open on top of osbot and still expect it not to crash.

 

Almost everyone i've asked have said, yeah i got this amazing computer it can do all these things, like run Lol, live stream ,youtube, WoW, runescape AND OSbot at the same time, my computer isn't the problem, its the client! grrr!!!! *Doesn't realise that OSBot has memory leak and you cant have so many programs open at the same time because is stupid*

hmm thats a good point, I for one dont do anything else while botting, since im a stricly iphone 4s guy.

idk about others, since this doesnt happen on ***** or tri. sorry i had to mention them

does it mean its osbots fault? thats what i think.

I mean you guys cant fix a memory leak, why not just accept osbots lack of performance.

edit 

pointing blame blame blame. 

not accepting osbots lack of performance, like i said before.

Edited February 9, 201411 yr by nenkido

hmmm, i remember you saying to get a better pc. That would mean a bad pc would have this issue, and a good pc would not.

people with good specs also have this problem, so then it must be osbot.

your'e original response was in osbots defence.

 

 

No, it wasn't in OSBot's defense, if OSBot was written correctly in the first place, memory leak wouldn't be happening.

It is still my opinion, that better PC is less likely to have the mentioned issues, EOT, unless you have anything new to add.

Yeah and those people probably haven't restarted their PC to nullify the effect of the memory leak before leaving it on for 10 hours overnight in which all the lost memory from the other programs are still amidst making no difference whether they're open/closed, you've still lost memory, and the memory leak is still in effect.

 

This is true, but nullify you say?

hmm thats a good point, I for one dont do anything else while botting, since im a stricly iphone 4s guy.

idk about others, since this doesnt happen on ***** or tri. sorry i had to mention them

does it mean its osbots fault? thats what i think.

I mean you guys cant fix a memory leak, why not just accept osbots lack of performance.

 

No one is denying OSBot is at fault for the memory leak, but it's your own incompetence that's causing the crash if your PC is good.

 

Here are my specs on my laptop:

 

 

I have never crashed, so if you have equal specs or better, then it's your own fault.

This is true, but nullify you say?

 

Resets the memory allocation back to default, thus nullifying the leak and restarting it upon computer restart.

No one is denying OSBot is at fault for the memory leak, but it's your own incompetence that's causing the crash if your PC is good.

 

Here are my specs on my laptop:

 

 

I have never crashed, so if you have equal specs or better, then it's your own fault.

 

Resets the memory allocation back to default, thus nullifying the leak and restarting it upon computer restar

do we even have an eta of osbot 2? or was all that just a troll,

 

Resets the memory allocation back to default, thus nullifying the leak and restarting it upon computer restart.

 

*Resets, does not equal null.

 

*Resets, does not equal null.

 

 

Ok, lets turn common english into technical english and say zero, not null. I hope you understand what zero means then.

do we even have an eta of osbot 2? or was all that just a troll,

 

It's under testing by the scripters atm.

Ok, lets turn common english into technical english and say zero, not null. I hope you understand what zero means then.

 

That's my point. You are only resetting the effect, so you cannot conclude there to be no memory leak. Lol