TEEMOLEGEND420 Posted September 16, 2016 Share Posted September 16, 2016 My java is updated idk, I can play on osbuddy fine, but when I go on osbot client it crashes after 2 mins of logging in. http://osbot.org/forum/topic/106146-client-crashes-after-a-minute/?hl=binary knew i wasnt the only one can someone please help me? Quote Link to comment Share on other sites More sharing options...
Token Posted September 16, 2016 Share Posted September 16, 2016 Start from CLI and give it an invalid memory allocation value like -mem j, check how much memory is allocated by default Quote Link to comment Share on other sites More sharing options...
TEEMOLEGEND420 Posted September 16, 2016 Author Share Posted September 16, 2016 Start from CLI and give it an invalid memory allocation value like -mem j, check how much memory is allocated by default How do I do that exaclty? Quote Link to comment Share on other sites More sharing options...
TEEMOLEGEND420 Posted September 16, 2016 Author Share Posted September 16, 2016 does no one know the solution to this? Quote Link to comment Share on other sites More sharing options...
TEEMOLEGEND420 Posted September 17, 2016 Author Share Posted September 17, 2016 wow Quote Link to comment Share on other sites More sharing options...
venetox Posted September 17, 2016 Share Posted September 17, 2016 (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 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. 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 September 17, 2016 by venetox Quote Link to comment Share on other sites More sharing options...
TEEMOLEGEND420 Posted September 18, 2016 Author Share Posted September 18, 2016 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 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. 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. Quote Link to comment Share on other sites More sharing options...
venetox Posted September 18, 2016 Share Posted September 18, 2016 idk man it couldnt find my ,jar file and i renamed it and all. Rename your jar to just "osbot.jar" then have it in your C drive and just use cd C:\ then java -jar "C:\osbot.jar" -XX:ErrorFile=C:/log/java/osbot_error.log Quote Link to comment Share on other sites More sharing options...