[arbiter]

RS3 after ~6 hours of runtime: RuneScape appears to have been closed or disconnected.

WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=57652] throws
java.lang.OutOfMemoryError: unable to create new native thread
   at java.lang.Thread.start0(Native Method)
   at java.lang.Thread.start(Thread.java:691)
   at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943)
   at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1336)
   at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:402)
   at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:359)
   at java.lang.Thread.run(Thread.java:722)

 

[american express]

Doesn't the RS3 client auto-log you out and refuse to let you log back in after 6 hours anyway? It forces you to reload the client and log in again.

Or is what you experienced different to that?

Just seems a coincidence to occur at the 6 hour mark.

 

[arbiter]

Doesn't the RS3 client auto-log you out and refuse to let you log back in after 6 hours anyway? It forces you to reload the client and log in again.

Or is what you experienced different to that?

Just seems a coincidence to occur at the 6 hour mark.

Jagex extended the six hour limit to 23 hours. Regardless, this issue is not related to that. This is a JVM crash caused by there not being anymore memory to allocate in the VM.