Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!
RuneMate will permanently shut down on August 7, 2026
due to events outside our control. You can continue using RuneMate until this date after which it will no longer be available. Thank you to everyone that contributed to RuneMate's success and to the community for the opportunity to serve you all these years.

  • Learn about RuneMate Vault and how its zero knowledge local encryption already protects your sensitive information.
  • Edit or delete your RuneMate account from your Account Settings.
  • All account upgrade subscriptions have been cancelled. No action required.

Resolved RS3 Crashed

Joined
Dec 18, 2014
Messages
398
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:
Exception in thread "GameSetup" (12:44:30) i
(12:44:30)     at e.a(e.java:43)
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:54)
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:61)
(12:44:30)     at Rs2Applet.init(Rs2Applet.java:344)
(12:44:30)     at app.un.new(efb:147)
(12:44:30)     at app.EO.run(ygc:123)
(12:44:30) Caused by: java.lang.RuntimeException: i
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:52)
(12:44:30)     ... 4 more
(12:44:30) Caused by: i
(12:44:30)     at e.a(e.java:43)
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:54)
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:61)
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:97)
(12:44:30)     at Rs2Applet.init(Rs2Applet.java:342)
(12:44:30)     ... 2 more
(12:44:30) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:52)
(12:44:30)     ... 5 more
(12:44:30) Caused by: java.lang.reflect.InvocationTargetException
(12:44:30)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
(12:44:30)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
(12:44:30)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
(12:44:30)     at java.lang.reflect.Method.invoke(Method.java:497)
(12:44:30)     at Rs2Applet.a(Rs2Applet.java:91)
(12:44:30)     ... 3 more
(12:44:30) Caused by: aqs
(12:44:30)     at ps.o(pt.java:71)
(12:44:30)     at client.init(client.java:1316)
(12:44:30)     ... 8 more
(12:44:30) Caused by: java.lang.NumberFormatException: For input string: "false"
(12:44:30)     at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
(12:44:30)     at java.lang.Integer.parseInt(Integer.java:580)
(12:44:30)     at java.lang.Integer.parseInt(Integer.java:615)
(12:44:30)     at client.init(client.java:1292)
(12:44:30)     ... 8 more
 
Joined
Mar 4, 2015
Messages
17
download and install jdk 8 (google it first link) be sure to remove all java versions before install
 
Joined
Dec 18, 2014
Messages
398
download and install jdk 8 (google it first link) be sure to remove all java versions before install
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.
 
Joined
Mar 9, 2015
Messages
7
is there anything i can do to fix this i'm still having this issue... and another thing is osrs loads just fine
 
Joined
Dec 18, 2014
Messages
398
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?
 
Last edited:
Top