Memory leak mate

If that's the case, then why aren't mind closing out at all?

I really don't want to but it keeps getting worse it literally wont run past ten minuts anymore, its just aggravating

been laughing for 5 mins lmao

i have 12gb of ram a pretty good computer overall and it happens to me randomly.

 

Sometimes it runs fine for days other times it crashes 1-2 times in day but I haven't had a issue so far with .79

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

 

If that's the case, then why aren't mind closing out at all?

My specs are good lol. It's not like the top model i7 hyperthreaded ssd with lots of RAM is the only optimal solution. Please specify, then, if you know what you are talking about.

I've noticed it closes out when I have no other programs running (like leaving it overnight and afk), however when I am active on my computer like I have been today it's running 5+ hours. That being said, it is definitely CPU related/memory leak but it doesn't take a lot of processing power and RAM to run a single instance of a bot.

My specs are good lol. It's not like the top model i7 hyperthreaded ssd with lots of RAM is the only optimal solution. Please specify, then, if you know what you are talking about.

I've noticed it closes out when I have no other programs running (like leaving it overnight and afk), however when I am active on my computer like I have been today it's running 5+ hours. That being said, it is definitely CPU related/memory leak but it doesn't take a lot of processing power and RAM to run a single instance of a bot.

 

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.

Sorry to see you leave but the developers are busy with OSBot 2 so you might have to bear with it. I'm not sure what the issue really is since it's never occurred to me but it may even be your computer's specs.

 

 

Osbot 2 EST 11/09/2153

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.

 

Explain to me how the memory leak takes affect.

 

Explain to me how the memory leak takes affect.

 

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

It will sometimes close for me while I'm sleeping but everytime I monitor it, it doesn't close. It's kinda weird.

i have 12gb of ram a pretty good computer overall and it happens to me randomly.

 

Sometimes it runs fine for days other times it crashes 1-2 times in day but I haven't had a issue so far with .79

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

 

 

 

i have 12gb of ram a pretty good computer overall and it happens to me randomly.

 

Sometimes it runs fine for days other times it crashes 1-2 times in day but I haven't had a issue so far with .79

 

 

 

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

  hmm well if you can prove what you claim mabye i woudn't doubt you. Can you prove that it is effected by specs?

I didn't always have this glitch tbh osbot used to be almost perfect. I remember when i didn't even get the random talking solver that makes my bot stick in one spot for hours.

It seemed like recently this started happening, so woudn't it be just a shittier osbot?It seems others have the same problem with good specs so you must be wrong....

Edited February 9, 201411 yr by nenkido

 

 

  hmm well if you can prove what you claim mabye i woudn't doubt you. Can you prove that it is effected by specs?

I didn't always have this glitch tbh osbot used to be almost perfect. I remember when i didn't even get the random talking solver that makes my bot stick in one spot for hours.

It seemed like recently this started happening, so woudn't it be just a shittier osbot?It seems others have the same problem with good specs so you must be wrong....

 

 

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.

EDIT: reading wiki

 

 

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.

 

 

I have 8 GB RAM and L3 cache and my overall pc performance does not change one bit as an effect of memory leak. It is definitely program-oriented.

Edited February 9, 201411 yr by ScriptsPl0x

EDIT: reading wiki

 

 

I have 8 GB RAM and L3 cache and my overall pc performance does not change one bit as an effect of memory leak. It is definitely program-oriented.

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

 

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.

 

 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.

Edited February 9, 201411 yr by nenkido