[salvation]

Edit: It's an AgentInitializationException, I don't know why I fucked up the title.

Yesterday Java updated itself on my machine and fucked everything up, so today I uninstalled all Java versions, RuneMate and OSRS.

I proceeded to install RuneMate and it downloaded JRE 1.8.0_121 during setup. I then installed OSRS. When looking in my software list, Java is not listed. RuneMate starts correctly but does not want to bind to OSRS. If launching RuneMate through CMD, it does not even see OSRS.

So, time to uninstall everything again. This time I installed JDK 1.8.0_151 on my system, followed by RuneMate (which again downloaded JRE 1.8.0_121) and then OSRS. Same story.

So then I tried installing OSRS before installing RuneMate, and it also gives the same result.

I've tried everything I could find on the forums.
 
Just tried with installing JRE 1.8.0_121 onto my system before installing anything else, also doesn't work.
 
Bump

 

[daniel]

Use 32bit Java.

 

[salvation]

Use 32bit Java.

Forgot to add that in the post, yes. All versions are tried were x86, so that's not the issue
There's no x64 version on my system, at all.

 

[party]

This seems to happen at random to people after Java updates - I don't even think we know the specific cause. @Cloud did we ever get anywhere with this?

@Salvation if you still have the logs (Help > View Logs if you can't find them) can you see if it ran with the packaged JRE (u121) every time, and if so, try running the standalone with whatever the latest version is (I think it's u151)?

EDIT: If you have been running with the standalone version, try running the Windows installer version instead (presuming you're on Windows).

 

[salvation]

This seems to happen at random to people after Java updates - I don't even think we know the specific cause. @Cloud did we ever get anywhere with this?

@Salvation if you still have the logs (Help > View Logs if you can't find them) can you see if it ran with the packaged JRE (u121) every time, and if so, try running the standalone with whatever the latest version is (I think it's u151)?

EDIT: If you have been running with the standalone version, try running the Windows installer version instead (presuming you're on Windows).

I tried installer and standalone, but didn't know about the logs so I'll do it again tomorrow (no time today) and post the results.

Strange thing is that before updating Java, everything worked and the update broke it all. I figured removing all installations and then re-installing using the steps provided by the forums would work, but so far no luck.
 
cleaned my computer, including a lot of data (appdata, programdata, etc) that contained jagex, runescape or java. Rebooted and then installed runemate using the installer. Finished the installer without opening runemate. I then installed OSRS and clicked the button in my browser to allow jagex-nav to be resolved. OSRS booted fine. This is all without installing java myself.

At this point I notice that both runemate and osrs are installed on C, but the newly created jagexcache is in D. I closed osrs and deleted the jagexcache.

I now run runemate and it complains that it cannot launch osrs using jagex-nav, so this is probably caused by me deleting the jagexcache. I completely uninstalled osrs and re-installed it. Now the jagex-nav is working again. After re-opening runemate, it is able to launch a new game client. It detects the game client and I am able to start the instance, but then I get the same error again: AgentInitializationException.

This is the log:

[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.68.2
[Debug] Operating System: Windows 10 x64
Nov 05, 2017 12:17:37 PM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Checking for a new game client every second for two minutes or until one is found.
Found a new game instance after 15 seconds.
com.sun.tools.attach.AgentInitializationException: Agent JAR loaded but agent failed to initialize
    at sun.tools.attach.HotSpotVirtualMachine.loadAgent(lw:75)
    at nul.iIiIiIiiIiiii.int(xmc:192)
    at nul.IiIIiIiiIIiiI.run(shc:60)

 
Now with standalone:

 
@Arbiter I really need some help here man, I don't understand this

 

[party]

I really need some help here man, I don't understand this

That's part of the problem, we don't really understand it either... Take it you've tried running both from C rather than split between C and D?

EDIT: Any idea if the RS client stores logs locally?
 
Okay if you try again and then locate the hs_err_pidXXXX.log files in your jagexcache/jagexlauncher/bin, see if you can spot an exception being thrown when RuneMate tries to attach.

 

[salvation]

Will try later, but as far as I know I cannot make OSRS use C only. It's installed on C and still uses D for the cache =/
But that's always been the case... so yeah

 

[parametric]

Out of curiosity have you tried java version 144 or 151? I've noticed function differences between versions.

 

[arbiter]

@Cloud

 

[cloud]

Hey old friend, join our slack channel so we can debug that specific bug better. I have a pretty good idea of the problem and a fix in this case, I just need some more information and some catching up would be chill. Anyways, the first piece of information I need is where exactly on your D drive is the jagexcache/jagexlauncher/bin folder located? It's normally in your home folder on the C drive but I need an exact file path. You can message it to me on slack directly if you risk posting your full name by pasting the path because I'm not sure if you're still comfortable with people knowing it (although I know you were for a time) @Salvation