Jump to content

java(tm) platform se binary has stopped working


Recommended Posts

Posted (edited)

lIn order for anyone to be able to help you will need to post some kind of error log.

 

To do this launch your osbot jar in an administrator command line with this command.

If you are on Windows 10 you can hold Win + X then press A this will launch an admin command prompt.

Otherwise open start menu and search cmd.exe then right click run as administrator.

 

Navigate to your osbot folder with the following command.

cd "YourOsbotFolder"

 

for example mine is in C:\Users\Harle\Documents\Osbot so I use

 

cd "C:\Users\Harle\Documents\Osbot"

 

then if your command prompt now looks like this

 

LWHLBTK.png

 

You can then paste the following command. You may need to replace "osbot 2.4.89.jar" with the name of your jar keeping the quotes and including the .jar if you have changed the name of your jar.

 

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log

 

It should now look like this and the cursor "little underscore" will be flashing just sitting there.

2FOVs2I.png

 

Now go through what you would normally do to cause osbot to crash.

 

When it crashes navigate to C:/log/java/osbot_error.log, open osbot_error.log and upload it all to pastebin.com then link the pastebin.

If any errors appear in your command prompt, copy and paste them to a separate paste on pastebin and link it also. 

There may also be log files inside the folder with your osbot jar file, put their contents in a pastebin also.

After you have done this, me and other people will be able to help.

 

 

You may also want to try the following things which could fix it.

 

When in a command prompt again at your osbot folder try.

 

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log -Xms256m -Xmx1024m

 

or

 

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log -mem j

 

Along with any other things people recommend via a command prompt.

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log

Edited by venetox
Posted

lIn order for anyone to be able to help you will need to post some kind of error log.

 

To do this launch your osbot jar in an administrator command line with this command.

If you are on Windows 10 you can hold Win + X then press A this will launch an admin command prompt.

Otherwise open start menu and search cmd.exe then right click run as administrator.

 

Navigate to your osbot folder with the following command.

cd "YourOsbotFolder"

 

for example mine is in C:\Users\Harle\Documents\Osbot so I use

 

cd "C:\Users\Harle\Documents\Osbot"

 

then if your command prompt now looks like this

 

LWHLBTK.png

 

You can then paste the following command. You may need to replace "osbot 2.4.89.jar" with the name of your jar keeping the quotes and including the .jar if you have changed the name of your jar.

 

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log

 

It should now look like this and the cursor "little underscore" will be flashing just sitting there.

2FOVs2I.png

 

Now go through what you would normally do to cause osbot to crash.

 

When it crashes navigate to C:/log/java/osbot_error.log, open osbot_error.log and upload it all to pastebin.com then link the pastebin.

If any errors appear in your command prompt, copy and paste them to a separate paste on pastebin and link it also. 

There may also be log files inside the folder with your osbot jar file, put their contents in a pastebin also.

After you have done this, me and other people will be able to help.

 

 

You may also want to try the following things which could fix it.

 

When in a command prompt again at your osbot folder try.

 

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log -Xms256m -Xmx1024m

 

or

 

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log -mem j

 

Along with any other things people recommend via a command prompt.

java -jar "osbot 2.4.89.jar" -XX:ErrorFile=C:/log/java/osbot_error.log

idk man it couldnt find my ,jar file and i renamed it and all.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...