1. OSBot Version (do NOT put "current version", be specific)

  2.5.89 injection

2. A description of the issue. Include relevant logs.

  When I checked the client, it was frozen with the GE open. I believed the last interaction it tried to do was interacting with the ring slot while it was open.

3. Are you receiving any errors in the client canvas or the logger? 

Error: df.ij() df.ij() df.ij() ha.ix() df.ij() df.ij() df.ij() ha.ix() client.fw() client.aq() bw.u() | lv:226 df:8900 df:8803 df:8802 ha:8660 df:8806 df:8802 df:8802 ha:8660 client:3919 client:1225 bw:360 bw:314 Thread:748 | java.lang.ArrayIndexOutOfBoundsException: 385344
error_game_crash
java.lang.NullPointerException
	at org.osbot.rs07.input.mouse.ClientMouseEventHandler.generateBotMouseEvent(xk:158)
	at org.osbot.rs07.input.mouse.MoveMouseEvent.IiIiIiiiIiII(ek:636)
	at org.osbot.rs07.input.mouse.MoveMouseEvent.IiIiIiiiIiII(ek:598)
	at org.osbot.rs07.input.mouse.MoveMouseEvent.execute(ek:88)
	at org.osbot.rs07.event.EventExecutor.IIiIiiiIIiII(cn:74)
	at org.osbot.rs07.event.EventExecutor.execute(cn:36)
	at org.osbot.rs07.script.MethodProvider.execute(on:539)
	at org.osbot.rs07.event.InteractionEvent.IiIiIiiiIiII(cl:143)
	at org.osbot.rs07.event.InteractionEvent.execute(cl:324)
	at org.osbot.rs07.event.EventExecutor.IIiIiiiIIiII(cn:74)
	at org.osbot.rs07.event.EventExecutor.execute(cn:36)
	at org.osbot.rs07.script.MethodProvider.execute(on:539)
	at org.osbot.rs07.api.Tabs.open(rg:44)
	at org.osbot.rs07.api.Tabs.open(rg:205)
	at org.osbot.rs07.event.InteractionEvent.execute(cl:659)
	at org.osbot.rs07.event.EventExecutor.IIiIiiiIIiII(cn:74)
	at org.osbot.rs07.event.EventExecutor.execute(cn:36)
	at org.osbot.rs07.script.MethodProvider.execute(on:539)
	at org.osbot.rs07.api.Equipment.interact(wh:757)
	at org.osbot.rs07.api.util.ItemContainer.interact(bh:764)

4. How can you replicate the issue?

  happened to 1 out of 100 accounts, probably cant replicate that

5. Has this issue persisted through multiple versions? If so, how far back?

  n/a

This looks like an client crash, not a bot crash. Not sure why you're getting this but if you can find a way to replicate it, I'll check it out

this was probably the result of a resource-starved vps, can probably close this