Resolved Combobox freezes bot after W10 upgrade

Discussion in 'Client & Site Support' started by Hakuna Matata, Aug 6, 2015.

  1. I recently upgraded from Windows 8 to Windows 10.
    But I can no longer click on comboboxes because it freezes the bot, as shown on the picture. It never loads and I have to terminate the Java process.

    At first I thought it was a problem with Alpha bots but it happens on all bots with comboboxes, except one.

    --- Double Post Merged, Aug 9, 2015, Original Post Date: Aug 6, 2015 ---
    Does anyone know why this is happening?
    I'm unable to use any bots after upgrading.

  2. Best Answer:
    Post #14 by Cloud, Aug 31, 2015
  3. I am experiencing the same issue.

    I have attempted : allocating more memory, Changing interface to oldschool style (helped a little. but certain boxes still did it)

    It's also caused me to lose 3 hours worth of $ through runemate on a paid bot:/
    please help anyone!
  4. Yeah, it's still happening. Haven't found a fix for it yet.
    It's only happening on Windows 10, so I'm pretty sure it's an issue with Java (?).
  5. Is there a log file from the jvm crashing anywhere?
  6. @Hakuna Matata @alpinestars Java version please.
    --- Double Post Merged, Aug 27, 2015, Original Post Date: Aug 27, 2015 ---
    Also get us that dump log and tell us specifically a few bots that have this issue.
  7. @Cloud no error or crash report on the jvm log that runs when i open the bat file.

    @Arbiter java 8 update 60, if i knew how to get the dump log i'd love to get that for you:p ill look into it. for me it has happened on Pixie FDK and Alpha Slayer so far. could possibly be from updating to windows 10? i will pull out my windows 8 laptop and try it on there.

    It works great on my windows 8.1

    (09:16:39) [Debug] Version: 1.1.16
    (09:16:39) [Debug] Operating System: Windows 10 (x64)
    (09:16:39) [Debug] Java: 8 Update 60 (x64)
    (09:17:15) [Setup] Downloading game...
    (09:17:52) [Setup] Syncing with RuneMate Cloud (a04eacb4)...
    (09:25:20) Our combat mode is: Revolution
    (09:25:20) Our combat mode is: Revolution

    is this right?
    #6 alpinestars, Aug 27, 2015
    Last edited: Aug 27, 2015
  8. @Arbiter No exceptions or anything is shown in the log. Java Version 8 Update 60 (build 1.8.0_60-b27)
    I will get you a list of bots that doesn't work and a few that works (I believe I found óne).
    --- Double Post Merged, Aug 28, 2015, Original Post Date: Aug 28, 2015 ---
    Doesn't work in any Alpha bot, any Celestial bot, any SS bot, most bots actually.
    It doesn't work, when the combobox looks like this:
    But it does work in TenPortables, where the combobox looks like this:
  9. Tested Alpha Runecrafting and it worked fine on Windows 10 with Java 8 Update 60. Please give me a specific bot name that crashes for you.

  10. SS Bonfires
  11. Just tested it and it works just fine. Try updating your graphics driver from the vendor's website, NOT Windows Update. I will additionally check on another Windows 10 computer to see if it occurs there.
  12. I'll try that, thanks!
    --- Double Post Merged, Aug 28, 2015, Original Post Date: Aug 28, 2015 ---
    @Arbiter I updated my drivers, they were very outdated, apparently.
    But it didn't fix the issue, sadly.

    Alpha Runecrafter works fine for me as well. It's the only one I've found that works.
  13. I was having this issue back in beta10. Somebody came to the conclusion that it maybe JavaFx that's the issue. I have the latest drivers and it was still crashing. No logs were being generated either.
  14. Found the error and solution here:

    It hangs the application, when you're clicking on a combobox that isn't focused.
    You can use the tab key to focus on the combobox and then click it. This will prevent the application from hanging.

    A combobox in focus:

    A combobox out of focus:

    This is not an issue with Java or RuneMate. It's an error with JavaFX, which many bot authors uses to make the GUI's for their bots.
    #13 Hakuna Matata, Aug 31, 2015
    Last edited: Aug 31, 2015
    synntax likes this.
  15. It appears that the bug has been documented here
    Unfortunately that means it is out of our control and we cannot fix it. You need to wait for the bug to be fixed within java. If you're familiar with how the JRE error reporting system work, feel free to comment on their page. If there were more comments it may raise the priority of the issue.
    synntax likes this.
  16. Thanks guys!


Share This Page