Well when I try to run OSBot using IntelliJ i get this stack:

//***************************************************************************\\
   OSBot Bot
   Copyright (C) OSBot.org
   Running Windows 7 on a(n) amd64 architecture
   Java version is 1.7.0_21
\\***************************************************************************//
 
[ERROR][12/02/13 11:17:33 PM]: Failed to load database module!
java.sql.SQLException: out of memory
at org.sqlite.DB.throwex(DB.java:380)
at org.sqlite.NestedDB._open(NestedDB.java:77)
at org.sqlite.DB.open(DB.java:91)
at org.sqlite.Conn.<init>(Conn.java:149)
at org.sqlite.Conn.<init>(Conn.java:49)
at org.sqlite.JDBC.connect(JDBC.java:86)
at java.sql.DriverManager.getConnection(DriverManager.java:579)
at java.sql.DriverManager.getConnection(DriverManager.java:243)
at org.osbot.V.<init>(ce:218)
at org.osbot.HA.g(tn:13)
at org.osbot.x.run(ee:220)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)

And OSBot closes right after it.

If I run it double clicking the jar it works perfectly!

Any idea how to fix this?

 

Why do you want to run it with IntelliJ? Just run OSBot once and as you update your script just keep replacing the new .JAR in the scripts folder and refresh the scripts page thing

I want to run on IntelliJ because its easier for me to send the jar straight to the folder when i hit run!

I guess OSBot is not compatible with IntelliJ.

Ok found out it doesnt work for eclipse either!

Ok maybe its my problem!

I use eclipse and it works fine

You seem to be running out of memory

Try increasing it in your launch configuration.

You need more virtual memory probably, RAM is not always the case (Random access memory) your pc also uses Virtual memory that it uses to execute processes.

If you are trying to load a TON of bytecode, such as osbot (osbot API is written with intelliJ for the most part) you need a lot of memory

 

If something is wrong, or malfunctioning is happening, you could be having a memory leak, world of possibilities. But i think it's the first 1

No its not a memory problem! Got it fixed, i could use my project jre, i located it to the java one and TA-DA!

This thread can be closed now, thanks