Nitrousek

So many of these users are ban evading... it's unreal, if you actually check the statistics... most of the banned scammers come back.

Yep, still waiting for that 100h proggy!

Flesh crawlers, you need stats anyway XD

0/10

dafuq, 17, someone's been busy.

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.

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.

http://en.wikipedia.org/wiki/Memory_leak If a program has a memory leak and its memory usage is steadily increasing, there will not usually be an immediate symptom. Every physical system has a finite amount of memory, and if the memory leak is not contained (for example, by restarting the leaking program) it will sooner or later start to cause problems. Most modern consumer desktop operating systems have both main memory which is physically housed in RAM microchips, and secondary storage such as a hard drive. Memory allocation is dynamic - each process gets as much memory as it requests. Active pages are transferred into main memory for fast access; inactive pages are pushed out to secondary storage to make room, as needed. When a single process starts consuming a large amount of memory, it usually occupies more and more of main memory, pushing other programs out to secondary storage - usually significantly slowing performance of the system. Even if the leaking program is terminated, it may take some time for other programs to swap back into main memory, and for performance to return to normal. When all the memory on a system is exhausted (whether there is virtual memory or only main memory, such as on an embedded system) any attempt to allocate more memory will fail. This usually causes the program attempting to allocate the memory to terminate itself, or to generate a segmentation fault. Some programs are designed to recover from this situation (possibly by falling back on pre-reserved memory). The first program to experience the out-of-memory may or may not be the program that has the memory leak.

There's no expression "take affect" that I know of.

Specs of the computer do play a role, if you have a weak computer, the OSBot client will close itself much more frequently. Client is closed by your computer, you know, when it reaches a point when memory leaked is too great for it to handle.

Wait, did you just...?

u wish, more like Mikasa

lol...................

Ofc they do, pls, no comment when you don't know what u talkin about.

Sure XD, that only proves my 1/10 was right ^^

1/10 I guess. Never seen you before.

Now this is something I did not want to see.

second time I see you, so 2/10

Don't worry, not releasing before OSBot 2 (probably several months)

Memory leak occours in OSBot 1, invest in a better PC.

My talent is over nine thousand.