Resolved RS3 Crashed

Discussion in 'Client & Site Support' started by Philosobyte, Mar 16, 2015.

  1. After the "Syncing with RuneMate" phase of starting the client, a message stating "RS3 Crashed!" pops up.
    Is this the issue with Java 1.8.0_40? Because I haven't had an issue with update 40 until the update today. Runescape's official client and Runescape in a browser still works finely.

    Code (Text):
    1.  
    2. Exception in thread "GameSetup" (12:44:30) i
    3. (12:44:30)     at e.a(e.java:43)
    4. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:54)
    5. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:61)
    6. (12:44:30)     at Rs2Applet.init(Rs2Applet.java:344)
    7. (12:44:30)     at app.un.new(efb:147)
    8. (12:44:30)     at app.EO.run(ygc:123)
    9. (12:44:30) Caused by: java.lang.RuntimeException: i
    10. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:52)
    11. (12:44:30)     ... 4 more
    12. (12:44:30) Caused by: i
    13. (12:44:30)     at e.a(e.java:43)
    14. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:54)
    15. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:61)
    16. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:97)
    17. (12:44:30)     at Rs2Applet.init(Rs2Applet.java:342)
    18. (12:44:30)     ... 2 more
    19. (12:44:30) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
    20. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:52)
    21. (12:44:30)     ... 5 more
    22. (12:44:30) Caused by: java.lang.reflect.InvocationTargetException
    23. (12:44:30)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    24. (12:44:30)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    25. (12:44:30)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    26. (12:44:30)     at java.lang.reflect.Method.invoke(Method.java:497)
    27. (12:44:30)     at Rs2Applet.a(Rs2Applet.java:91)
    28. (12:44:30)     ... 3 more
    29. (12:44:30) Caused by: aqs
    30. (12:44:30)     at ps.o(pt.java:71)
    31. (12:44:30)     at client.init(client.java:1316)
    32. (12:44:30)     ... 8 more
    33. (12:44:30) Caused by: java.lang.NumberFormatException: For input string: "false"
    34. (12:44:30)     at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
    35. (12:44:30)     at java.lang.Integer.parseInt(Integer.java:580)
    36. (12:44:30)     at java.lang.Integer.parseInt(Integer.java:615)
    37. (12:44:30)     at client.init(client.java:1292)
    38. (12:44:30)     ... 8 more


     
  2. Best Answer:
    Post #11 by Cloud, Mar 22, 2015
  3. @Cloud

    I don't believe this is related to u40 though.
     
  4. i am also getting rs3 crashed :(
     
  5. Must be a broken hook. @Cloud will deal with it ASAP.
     
  6. so is this being worked on? it is still crashing on me
     
  7. download and install jdk 8 (google it first link) be sure to remove all java versions before install
     
  8. I already have jdk8, naturally, being a developer. The client was working before the last update.

    The weird thing is that this is only happening to a few people. I tried deleting the cache in the RuneMate folder, then the entire folder. I also tried redownloading RuneMate. Nothing changed.
     
  9. Doesn't seem like a hook issue... it looks like the client itself is crashing...
     
  10. is there anything i can do to fix this i'm still having this issue... and another thing is osrs loads just fine
     
  11. At least three members have been unable to run RuneMate for 6 and a half days, by now. Is there a solution, or is there anything I can do to accelerate the process, or do we have to just wait for the next release?
     
    #10 Philosobyte, Mar 22, 2015
    Last edited: Mar 22, 2015
  12. I'll look into it a bit further and find the underlying cause.
     
  13. Issue resolved with version 77. Thank you.
     

Share This Page

Loading...