[kaisertazer]

Hello, been using the Spectre client since release.
Been perfect so far, minus that little 24/hr grace period in which it was downed by an RS3 update; but today I, and several others, have noticed an issue with the client;

We have noticed that bots which feature a loot/profit interface, such as alching, fishing, herb, etc.
Have been crashing every 5-15 minutes of usage, from screenshots I can only assume that it is related to the reproduction of data.


Here is one of the screenshots in question, as you can see the profit list has replicated the herbs, and ingredients several times over. It does this until eventually the bot stops, and the client presents an error message. I believe that the crash is being caused by the bot filling up the client's RAM limit.

Kudos to Dj for creating a temp fix, he suggested increasing the client's RAM limit, though I should mention;
This fix only adds and extra minute of runtime.

Hopefully this can be seen to shortly, if anyone has any other screenshots they'd like to share please do so here; so we can fix this.

Kaiser, out.

 

[savior]

That's up to the bot author.

 

[party]

@Aidden fix your damn loot tracker you noob

OP: This is definitely a bot issue. If it's happening on all the bots you use then that because you only use Maxi bots

 

[kaisertazer]

That's up to the bot author.

It's occurring on all bots, which leads me to believe it is client side.

 

[watertao876]

Spoiler

java.util.ConcurrentModificationException
at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:966)
at java.util.LinkedList$ListItr.next(LinkedList.java:888)
at com.sun.javafx.collections.ObservableSequentialListWrapper$2.next(ObservableSequentialListWrapper.java:111)
at java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1812)
at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464)
at robot.IIIIIiIIIi.case(lc:126)
at robot.IIIIIiIIIi.onItemAdded(lc:75)
at com.runemate.game.api.script bot.framework.core.EventDispatcher.process(fcb:144)
at nul.iIiIIIiIiIII.enum(dfb:203)
at nul.iiIiIIiiiiII.run(kfb:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

This is using Aiddens MaxiFletcher.

 

[savior]

It's occurring on all bots, which leads me to believe it is client side.

Then all the bots you used have this issue

 

[kaisertazer]

@Aidden fix your damn loot tracker you noob

OP: This is definitely a bot issue. If it's happening on all the bots you use then that because you only use Maxi bots

Qve, etc, having same issue.

 

[savior]

@Aidden fix your damn loot tracker you noob

shhh we can't flame him yet

 

[party]

It's occurring on all bots, which leads me to believe it is client side.

Loot tracker is bot specific - all RuneMate's API does is send ItemEvents down to the listeners and from there it's up to the bot author to decide what to do with them. Even if it was sending hundres of events per second the bot logic would still consolidate them into one entry if it was done properly.
 
@Savior can you verify against your fisher on bot store please?

 

[savior]

Loot tracker is bot specific - all RuneMate's API does is send ItemEvents down to the listeners and from there it's up to the bot author to decide what to do with them. Even if it was sending hundres of events per second the bot logic would still consolidate them into one entry if it was done properly.
 
@Savior can you verify against your fisher on bot store please?

what do you mean

 

[party]

what do you mean

Run the fisher, make sure ours isn't duplicating entries.

 

[savior]

Run the fisher, make sure ours isn't duplicating entries.

No it's working properly.

 

[party]

Then @Aidden and @qverkk get ur shit fixed

 

[aidden]

@Aidden fix your damn loot tracker you noob

OP: This is definitely a bot issue. If it's happening on all the bots you use then that because you only use Maxi bots

What do you think i've been trying to do m9. -.- I push an update unrelated and bam now the threading issue has kicked in again. This is pissing me off.
 

Spoiler

java.util.ConcurrentModificationException
at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:966)
at java.util.LinkedList$ListItr.next(LinkedList.java:888)
at com.sun.javafx.collections.ObservableSequentialListWrapper$2.next(ObservableSequentialListWrapper.java:111)
at java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1812)
at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464)
at robot.IIIIIiIIIi.case(lc:126)
at robot.IIIIIiIIIi.onItemAdded(lc:75)
at com.runemate.game.api.script bot.framework.core.EventDispatcher.process(fcb:144)
at nul.iIiIIIiIiIII.enum(dfb:203)
at nul.iiIiIIiiiiII.run(kfb:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

This is using Aiddens MaxiFletcher.

Fixed. The concurrency issues may still show up though although i expect them to be back to the frequency they were before today.

 

[party]

What do you think i've been trying to do m9. -.- I push an update unrelated and bam now the threading issue has kicked in again. This is pissing me off.
 

Fixed. The concurrency issues may still show up though although i expect them to be back to the frequency they were before today.

TrashiBots