1. OSBot Version (do NOT put "current version", be specific) 2.4.88
2. A description of the issue. Include relevant logs.

Client freezes with Java Platform SE binary has stopped working.

http://prntscr.com/cgjv0u
3. Are you receiving any errors in the client canvas or the logger?

No, it just stops.
4. How can you replicate the issue?

By launching the client.
5. Has this issue persisted through multiple versions? If so, how far back?

No it hasn't, it started to occur two days ago, but I'm pretty sure I was able to load the client on this version and run it successfully. 

 

What I've done:

-Reinstalled Java (OSBuddy works / another client (offsite that uses Java) works)

-Deleted the Osbot folder (local scripts/proxies/account settings) - This error occurs using no proxy and with proxies

-Checked for windows update/BIOS update etc etc

 

Please help! 

Reinstalled Java, why? Checking for BIOS update? This is a little overkill, let's start with some basics.

 

1. At what point does the client freeze?

-Is it in the boot menu?

-Is it right after the client interface appears?

-Is it after you add a bot?

-Is it when you start a script?

-Is it when it reaches the login menu?

 

2. The logger is only useful for debugging simple problems and scripts. Have you tried starting OSBot from command line using the flag "debug -5005"? If you are unsure how to do this, many people on this forum can help you with that.

It appears to freeze within two minutes after adding a bot, whether I log into the game or not. 

-I've also tried loading the runescape client to preload the game cache

-I've tried starting Osbot from the command line with no success

-There's no spike in CPU/Ram when it freezes. 

Has this issue been resolved?

It appears to freeze within two minutes after adding a bot, whether I log into the game or not. 

-I've also tried loading the runescape client to preload the game cache

-I've tried starting Osbot from the command line with no success

-There's no spike in CPU/Ram when it freezes. 

 

 

Has this issue been resolved?

 

I'm having the exact same issue on windows 10. Once loading the rsclient, it consistently takes around 1:15 until the it will crash, counting from the login screen to appear.

 

 

Edit: I found the solution. The issue is cause by the module "ltc_game64-116096.dll" which is in the application PlaysTV. Uninstalling it fixed the issue for me

Edited September 29, 20169 yr by tr1zym

 

I'm having the exact same issue on windows 10. Once loading the rsclient, it consistently takes around 1:15 until the it will crash, counting from the login screen to appear.

 

 

Edit: I found the solution. The issue is cause by the module "ltc_game64-116096.dll" which is in the application PlaysTV. Uninstalling it fixed the issue for me

 

 

Interesting, how did you find out about that?

Interesting, how did you find out about that?

 

Opened "Event Viewer" after the crash. Windows Logs > Applications, and the recent program errors showed up. The log displayed module name and folder location.

 

Has this issue been resolved with this fix @@Caesar