[wizax]

So I was doing fine for the past couple weeks but now when I try to open RuneMate and try to access bots, either I can't do more than 4 instances or after 3 RuneMate starts freezing and then there's messages saying I need to allocate more memory next time..

I did the -Xmx1300M as stated in the FAQ

Tried reinstalling both RuneMate and RuneScape

Tried testing my computer itself, nothing changed

I was using Quality Divination

Any suggestions?

Legit lost over 50 hours/4$+ trying to fix it
 
java.lang.OutOfMemoryError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
at java.util.concurrent.ForkJoinTask.get(ForkJoinTask.java:1005)
at nul.IIiiIIiiiiii.super(jeb:61)
at com.runemate.game.api.hybrid.queries.QueryBuilder.results(wza:114)
at nul.IIiiIIiiIiii.super(sya:99)
at nul.IIiiIIiiIiii.super(sya:157)
at nul.iIiIiIiIIiIi.validate(oeb:111)
at com.runemate.game.api.script.framework.LoopingBot.run(gbb:1)
at com.runemate.game.api.script.framework.AbstractBot.start(zza:160)
at nul.iIIiiIiiiIiI.run(ajb:13)
Caused by: java.lang.OutOfMemoryError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at java.util.concurrent.ForkJoinTask.getThrowableException(ForkJoinTask.java:598)
at java.util.concurrent.ForkJoinTask.reportException(ForkJoinTask.java:677)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:735)
at java.util.stream.ReduceOps$ReduceOp.evaluateParallel(ReduceOps.java:714)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at nul.IIiiIIiiiiii.super(jeb:185)
at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1424)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.HashMap.resize(HashMap.java:703)
at java.util.HashMap.putVal(HashMap.java:662)
at java.util.HashMap.put(HashMap.java:611)
at nul.iiiiIIiiIIiI.super(xab:76)
at nul.iiiIIIiIiIii.super(hib:4001)
at nul.iiiIIIiIiIii.super(hib:17362)
at nul.iIiIiIiiIiIi.super(kfb:149)
at nul.iIiiIIiiIiiI.super(deb:96)
at nul.iIiiIIiiIiiI.super(deb:177)
at com.runemate.game.api.hybrid.local.Varbits.load(pmb:146)
at nul.iiIIiIiiIIII.getLocalState(hrb:16262)
at com.runemate.game.api.hybrid.queries.GameObjectQueryBuilder.accepts(fpb:166)
at com.runemate.game.api.hybrid.queries.GameObjectQueryBuilder.accepts(fpb:73)
at com.runemate.game.api.hybrid.queries.QueryBuilder$$Lambda$522/16547718.test(Unknown Source)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceTask.doLeaf(ReduceOps.java:747)
at java.util.stream.ReduceOps$ReduceTask.doLeaf(ReduceOps.java:721)
at java.util.stream.AbstractTask.compute(AbstractTask.java:316)
at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
... 4 more
 
@kazemanie Kaze would you have a solution for this ?

 

[american express]

If you are only experiencing this issue with one bot, then post this issue in the relevant bot thread. It is most likely an issue caused from that bot itself, only.

 

[wizax]

Sigh, it's from Quality Divination, but the guy is apparently MIA, and his bots are apparently perfect, i'm fucked

Thanks for the fast reply @kazemanie I appreciate it alot

 

[abdo style]

I am having the same problems despite never having them before, my clients get extremely laggy and it will result in a crash after 2 hours.

 

[savior]

Judging by the stack trace it seems like a client issue to me.

 

[party]

We believe it may be a client issue caused by the recent QueryBuilder updates, and Cloud is currently working on a fix.