As title says. I am running 25 bots on one machine. One single more bot, and it claims I am out of memory. However I am only using 25.5GB of 32GB available. Maximum memory for each bot is 800mb, which adds to about 20GB with the 25 I am running. It can hold more fine. I attempted to go to stackoverflow to debug this issue, however it is basically impossible because I need access to verbose JVM logs and the client starts a new process which I can't pass the parameter to. Here is the log file from the crashes: https://pastebin.com/6gVWFA51

java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)

Windows 7 x64

 

Edited April 3, 20179 yr by dmmslaver

How do you know that the "maximum memory for each bot is 800mb"?

13 minutes ago, Alek said:

How do you know that the "maximum memory for each bot is 800mb"?

Quote

-mem 800

 Unless osbot memory command doesn't work? Or thats the initial size. If so then I need a maximum size flag lol 

EDIT: Jesus christ, java is running 32bit mode. I swore i checked that. Let me swap it over and see if it fixes the issue. If so, sorry for spam lmao. Will report back. 

Edited April 4, 20179 yr by dmmslaver

6 minutes ago, dmmslaver said:

 Unless osbot memory command doesn't work? Or thats the initial size. If so then I need a maximum size flag lol 

EDIT: Jesus christ, java is running 32bit mode. I swore i checked that. Let me swap it over and see if it fixes the issue. If so, sorry for spam lmao. Will report back. 

According to the CLI commands table, mem sets Xmx. Xmx sets the maximum heap for the JVM, while the stack is controlled by both your Operating System and Java. Smaller heap space means the more the JVM has to GC until there's just not enough heap space to support any new objects. 

Additionally your operating system may have reserve space which influences how much its willing to allocate to applications; on Windows I believe this is already calculated.

2 minutes ago, Alek said:

According to the CLI commands table, mem sets Xmx. Xmx sets the maximum heap for the JVM, while the stack is controlled by both your Operating System and Java. Smaller heap space means the more the JVM has to GC until there's just not enough heap space to support any new objects. 

Additionally your operating system may have reserve space which influences how much its willing to allocate to applications; on Windows I believe this is already calculated.

Yes, it was running java in 32bit mode. Sorry for wasting your time, am autistic lol even posted it on stackoverflow. Need to smoke less while coding ya feel 

Well still watch out because even setting it at "800", the total RAM will go over. Just assume that the stack will be 20% (Im pulling numbers from thin air). So if you set heap to  800mb, the overall client may use somewhere around 1GB.