1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Question Java OutOfMemoryError when logging into client opened by Intellij

Discussion in 'Developer Support' started by Adc2, Dec 19, 2021.

  1. Adc2

    Joined:
    Jun 6, 2021
    Messages:
    3
    Likes Received:
    0
    This appears to happen when all of the following are true:
    1) running runemate via intellij
    2) it's 32bit runemate
    3) JRE selected is x86/RuneMate/jre
    4) Runemate client login with correct username and password

    I've tried setting the client run arguments as follows:
    Code (Text):
    1. -sdk -Xms512M -XMX1024M
    as well as tried adjusting vmoptions to the same values

    but the max heap size still reports 248MB. for reference, when I run runemate directly (not via intellij) the max heap size per the logs is 990MB.

    Trying to figure out what's giving me this error:

    Code (Text):
    1.  
    2. "C:\Program Files (x86)\RuneMate\jre\bin\java.exe" [...]
    3. com.runemate.boot.Boot -sdk -Xms512M -Xmx1024M
    4. [Debug] Java Home: C:\Program Files (x86)\RuneMate\jre
    5. [Debug] Java Version: 1.8.0_301 x86 (Oracle Corporation)
    6. [Debug] Maximum Heap Size: 248MB
    7. [Debug] RuneMate Version: 2.114.11
    8. [Debug] Operating System: Windows 10 x64
    9. [Debug] C:\Users\Travis\OneDrive\jagexcache is a cache root according to the registry.
    10. Exception in thread "Thread-11" java.lang.OutOfMemoryError: Java heap space
    11.     at java.util.Arrays.copyOf(Arrays.java:3236)
    12.     at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:118)
    13.     at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
    14.     at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:153)
    15.     at nul.IiiIIIiiIiiIi.iIiiiiiiIiIIi(lqc:210)
    16.     at nul.IiiIIIiiIiiIi.iIiiiiiiIiIIi(lqc:21)
    17.     at nul.IiiIIIiiIiiIi.iIiiiiiiIiIIi(lqc:208)
    18.     at nul.IiiIIIiiIiiIi.iIiiiiiiIiIIi(lqc:155)
    19.     at nul.iIiiiIiiiIIii.iIiiiiiiIiIIi(tgc:481)
    20.     at nul.IIiIiIiiiIIIi.iIiiiiiiIiIIi(nac:8847)
    21.     at nul.IIiIiIiiiIIIi.IIiiiiiiiIiii(nac:1714)
    22.     at nul.IIiIiIiiiIIIi$$Lambda$362/1250928.run(Unknown Source)
    23.     at java.lang.Thread.run(Thread.java:748)
    24.  
    My vmoptions:
    Code (Text):
    1.  
    2. -Xms512m
    3. -Xmx1024m
    4. -XX:ReservedCodeCacheSize=240m
    5. -XX:+UseConcMarkSweepGC
    6. -XX:SoftRefLRUPolicyMSPerMB=50
    7. -ea
    8. -XX:CICompilerCount=2
    9. -Dsun.io.useCanonPrefixCache=false
    10. -Djava.net.preferIPv4Stack=true
    11. -Djdk.http.auth.tunneling.disabledSchemes=""
    12. -XX:+HeapDumpOnOutOfMemoryError
    13. -XX:-OmitStackTraceInFastThrow
    14. -Djdk.attach.allowAttachSelf
    15. -Dkotlinx.coroutines.debug=off
    16.  
    After attempting to log in to runemate launched via Intellij the loading wheel will spin forever.
    --- Double Post Merged, Dec 19, 2021, Original Post Date: Dec 19, 2021 ---
    Resolved through Discord. memory arguments needed to be added to VM options line in the Spectre run configuration instead of directly to the application's arguments.
    unknown.png arguments line.png
     

Share This Page

Loading...