Jump to content

Error #2


iJodix

Recommended Posts

Happened when it tried to load new region aka "Loading - please wait."

[ERROR][Bot #1][03/06 08:02:41 AM]: Error on random executor!
java.lang.RuntimeException: Read timeout
	at client.nat.stream.Stream.m14(Native Method)
	at client.emu.Static.getCacheInt(Unknown Source)
	at client.emu.EmuClient.getLoginState(Unknown Source)
	at org.osbot.rs07.api.Client.getLoginStateValue(bn:212)
	at org.osbot.rs07.api.Client.getLoginState(bn:241)
	at org.osbot.rs07.api.Client.isLoggedIn(bn:211)
	at org.osbot.rs07.randoms.WelcomeScreen.shouldActivate(jc:109)
	at org.osbot.rs07.event.RandomExecutor.run(wj:130)
	at java.lang.Thread.run(Unknown Source)

Link to comment
Share on other sites

  • Developer

 

Happened when it tried to load new region aka "Loading - please wait."

[ERROR][Bot #1][03/06 08:02:41 AM]: Error on random executor!
java.lang.RuntimeException: Read timeout
	at client.nat.stream.Stream.m14(Native Method)
	at client.emu.Static.getCacheInt(Unknown Source)
	at client.emu.EmuClient.getLoginState(Unknown Source)
	at org.osbot.rs07.api.Client.getLoginStateValue(bn:212)
	at org.osbot.rs07.api.Client.getLoginState(bn:241)
	at org.osbot.rs07.api.Client.isLoggedIn(bn:211)
	at org.osbot.rs07.randoms.WelcomeScreen.shouldActivate(jc:109)
	at org.osbot.rs07.event.RandomExecutor.run(wj:130)
	at java.lang.Thread.run(Unknown Source)

 

Seems like the client running rs crashed, could you post crash logs by any chance?

They will most likely be at a folder where your browser executable file is present.

Link to comment
Share on other sites

  • Developer

Did search the whole system, nothing.

Changed to Internet Explorer, works alright now.

 

How long did client run for until this happened?

Was it getting slower or less responsible?

Were you entering new regions often or staying in crowded places (lots of players/npcs)?

 

Before this happens again, go to your control panel, select java.

Something like this should open:

114c311ee0.png

Select Show console, and apply the changes.

Then once the crash happens, press m and g to print memory usage and then copy the contents of console here.

Link to comment
Share on other sites

How long did client run for until this happened?

Was it getting slower or less responsible?

Were you entering new regions often or staying in crowded places (lots of players/npcs)?

The client ran for like 10 mins or so.

The place where i bot isn't crowded at all, like a couple of people only.

Currently running on Chrome again to see when the problem exactly occurs.

Link to comment
Share on other sites

Make sure you have the console enabled.

The Java console was open, and once the java crashed, it decided to crash too and close itself and i couldn't re-open the console.

[ERROR][Bot #1][03/06 04:20:36 PM]: Error on random executor!
java.lang.RuntimeException: Read timeout
	at client.nat.stream.Stream.m14(Native Method)
	at client.emu.Static.getCacheInt(Unknown Source)
	at client.emu.EmuClient.getLoginState(Unknown Source)
	at org.osbot.rs07.api.Client.getLoginStateValue(bn:212)
	at org.osbot.rs07.api.Client.getLoginState(bn:241)
	at org.osbot.rs07.randoms.BreakManager.shouldActivate(jd:45)
	at org.osbot.rs07.event.RandomExecutor.run(wj:130)
	at java.lang.Thread.run(Unknown Source)

1j2fl1.png

Edited by iJodix
Link to comment
Share on other sites

  • Developer

The Java console was open, and once the java crashed, it decided to crash too and close itself and i couldn't re-open the console.

[ERROR][Bot #1][03/06 04:20:36 PM]: Error on random executor!
java.lang.RuntimeException: Read timeout
	at client.nat.stream.Stream.m14(Native Method)
	at client.emu.Static.getCacheInt(Unknown Source)
	at client.emu.EmuClient.getLoginState(Unknown Source)
	at org.osbot.rs07.api.Client.getLoginStateValue(bn:212)
	at org.osbot.rs07.api.Client.getLoginState(bn:241)
	at org.osbot.rs07.randoms.BreakManager.shouldActivate(jd:45)
	at org.osbot.rs07.event.RandomExecutor.run(wj:130)
	at java.lang.Thread.run(Unknown Source)

1j2fl1.png

 

My guess is that crash occurs due to browser client running out of memory after some time as heap size is limited to 256 MB.

To confirm that, could you try running in crowded areas with alot of players/npcs/objects?

And keep pressing g and m every once a while on the console to track the available memory

 

Link to comment
Share on other sites

My guess is that crash occurs due to browser client running out of memory after some time as heap size is limited to 256 MB.

To confirm that, could you try running in crowded areas with alot of players/npcs/objects?

And keep pressing g and m every once a while on the console to track the available memory

 

350l9iw.png

You're right, the memory went to 1% just before it started to load new arena and when it started to load, everything crashed and the console closed itself. I wasn't that quick to take picture x)

Edited by iJodix
Link to comment
Share on other sites

  • Developer

350l9iw.png

You're right, the memory went to 1% just before it started to load new arena and when it started to load, everything crashed and the console closed itself. I wasn't that quick to take picture x)

 

I'l make a new build later today with greatly reduced model buffers count, that should fix this issue.

Thanks for your feedback.

  • Like 4
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...