Unsure what the cause may be, but sometimes if I close the bot in mirror mode, the RS applet ends up going black and doesn't go back. When I refresh the page and click "Run" on the applet popup, Chrome then freezes forcing me to kill the process and launch it again. There were no errors in the IntelliJ debug console, but I did notice a bunch of hs_err_pidXXXX.log files.
Mirror 1.0.52
Chrome 41.0.2272.101
Firefox 35.0.1
java version "1.8.0_40"
Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
Java HotSpot(TM) Client VM (build 25.40-b25, mixed modeNo hooks failed)
Looking into the file, this looks useful.
Stack: [0x4d580000,0x4d5d0000], sp=0x4d5cf0e8, free space=316k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ewwr4320176462043285293.dll+0x7bcf]
J 2189 client.nat.stream.Stream.m16(JI)I (0 bytes) @ 0x02b7ab2f [0x02b7aaa0+0x8f]
J 2155 C1 client.KNApAkkyGbM.sq()I (77 bytes) @ 0x02b51384 [0x02b512a0+0xe4]
j client.emu.EmuClient.getItemStorage()Lorg/osbot/rs07/accessor/XNodeContainer;+0
J 3021 C1 org.osbot.rs07.api.Inventory.getItems()[Lorg/osbot/rs07/api/model/Item; (156 bytes) @ 0x02976524 [0x029764b0+0x74]
j org.valkyr.api.framework.utils.LootTracker.getNewList()Ljava/util/List;+15
j org.valkyr.api.framework.utils.LootTracker.process()V+6
j org.valkyr.api.framework.utils.LootTracker.run()V+8
j java.lang.Thread.run()V+11
v ~StubRoutines::call_stub
When I try to start the client in mirror mode, I often see this error while the bot says "Connecting to client"
java.lang.InternalError: Remote thread failed for unknown reason
at sun.tools.attach.WindowsVirtualMachine.enqueue(Native Method)
at sun.tools.attach.WindowsVirtualMachine.execute(Unknown Source)
at sun.tools.attach.HotSpotVirtualMachine.executeCommand(Unknown Source)
at sun.tools.attach.HotSpotVirtualMachine.getAgentProperties(Unknown Source)
at client.emu.EmuClient$1.run(Unknown Source)
at client.eTXqkBG.pn(Unknown Source)
at client.emu.EmuClient.run(Unknown Source)
at java.lang.Thread.run(Thread.java:745)