Bug Official Client Crashes

Discussion in 'Client & Site Support' started by Arbiter, Apr 30, 2016.

  1. RS3 after ~6 hours of runtime: RuneScape appears to have been closed or disconnected.
    Code (Text):
    1. WARNING: RMI TCP Accept-0: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=57652] throws
    2. java.lang.OutOfMemoryError: unable to create new native thread
    3.    at java.lang.Thread.start0(Native Method)
    4.    at java.lang.Thread.start(Thread.java:691)
    5.    at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943)
    6.    at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1336)
    7.    at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:402)
    8.    at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:359)
    9.    at java.lang.Thread.run(Thread.java:722)
     
  2. 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.
     
  3. 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.
     
    kazemanie likes this.

Share This Page

Loading...