UNSOLVED Optimization and LiquidBounce

WYSI

Since I updated to LiquidBounce b73 beta (or b72), I've noticed a thing.
When I open LiquidBounce and play in 15 mins, nothing happen. But after a while, my FPS drops so much and lag spike occurs every 10 seconds. This make me can't play well and have to exit LiquidBounce.

Can you guy help me fix this please?

Litely

@Conclusion said in Optimization and LiquidBounce:

noticed

yes drop fps and so lag

@Conclusion Yea the is a way download memory fix mod it can fix that and it give you more fps ! i try it with LB and it work good

This post is deleted!

helloana

I experienced the same thing for b73 which is why I switched back to b72. It's a memory leak and it is a big annoyance.

Litely

try set this jvm it can help you
-Xmx2G -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+UseNUMA -XX:+CMSParallelRemarkEnabled -XX:MaxTenuringThreshold=15 -XX:MaxGCPauseMillis=30 -XX:GCPauseIntervalMillis=150 -XX:+UseAdaptiveGCBoundary -XX:-UseGCOverheadLimit -XX:+UseBiasedLocking -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -XX:+UseFastAccessorMethods -XX:+UseCompressedOops -XX:+OptimizeStringConcat -XX:+AggressiveOpts -XX:ReservedCodeCacheSize=2048m -XX:+UseCodeCacheFlushing -XX:SoftRefLRUPolicyMSPerMB=10000 -XX:ParallelGCThreads=10

idiot

@Conclusion memoryfixer:

 private TimerUtil timer = new TimerUtil();
    @EventTarget
    public void onTick(){
        if(timer.hasReached(3000)) {
            System.gc();
            //Runtime.getRuntime().gc();
            timer.reset();
        }
    }

TimerUtil:

 public static boolean hasReached(long milliseconds) {
        if (TimerUtil.getCurrentMS() - lastMS >= milliseconds) {
            return true;
        }
        return false;
    }

 public static long getCurrentMS() {
        return System.nanoTime() / 1000000L;
    }

  public static void reset() {
        prevMS = TimerUtil.getTime();
    }

 public static long getTime() {
        return System.nanoTime() / 1000000L;
    }

CzechHek

@idiot said in Optimization and LiquidBounce:

@Conclusion memoryfixer:

Again with Core...

module = {
    name: "MemoryFixer",
    author: "CzechHek",
    onUpdate: function () {
        timer.hasTimePassed(3000) && (Runtime.gc(), timer.reset());
    }
}

script.import("Core.lib");
timer = new MSTimer();
Runtime = Java.type("java.lang.Runtime").getRuntime();

WYSI

@idkmyname said in Optimization and LiquidBounce:

try set this jvm it can help you
-Xmx2G -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+UseNUMA -XX:+CMSParallelRemarkEnabled -XX:MaxTenuringThreshold=15 -XX:MaxGCPauseMillis=30 -XX:GCPauseIntervalMillis=150 -XX:+UseAdaptiveGCBoundary -XX:-UseGCOverheadLimit -XX:+UseBiasedLocking -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=15 -Dfml.ignorePatchDiscrepancies=true -Dfml.ignoreInvalidMinecraftCertificates=true -XX:+UseFastAccessorMethods -XX:+UseCompressedOops -XX:+OptimizeStringConcat -XX:+AggressiveOpts -XX:ReservedCodeCacheSize=2048m -XX:+UseCodeCacheFlushing -XX:SoftRefLRUPolicyMSPerMB=10000 -XX:ParallelGCThreads=10

my computer have 2 gb ram lmao

WYSI

@CzechHek said in Optimization and LiquidBounce:

@idiot said in Optimization and LiquidBounce:

@Conclusion memoryfixer:

Again with Core...

module = {
    name: "MemoryFixer",
    author: "CzechHek",
    onUpdate: function () {
        timer.hasTimePassed(3000) && (Runtime.gc(), timer.reset());
    }
}

script.import("Core.lib");
timer = new MSTimer();
Runtime = Java.type("java.lang.Runtime").getRuntime();

will try this after download memory fix mod

WYSI

@helloana said in Optimization and LiquidBounce:

I experienced the same thing for b73 which is why I switched back to b72. It's a memory leak and it is a big annoyance.

same experience

ChocoPie_isme

@CzechHek said in Optimization and LiquidBounce:

@idiot said in Optimization and LiquidBounce:

@Conclusion memoryfixer:

Again with Core...

module = {
    name: "MemoryFixer",
    author: "CzechHek",
    onUpdate: function () {
        timer.hasTimePassed(3000) && (Runtime.gc(), timer.reset());
    }
}

script.import("Core.lib");
timer = new MSTimer();
Runtime = Java.type("java.lang.Runtime").getRuntime();

flexing one line code script using core ^

Litely

@Conclusion so set 2G to 1G

WYSI

@ChocoPie_isme said in Optimization and LiquidBounce:

@CzechHek said in Optimization and LiquidBounce:
@idiot said in Optimization and LiquidBounce:

@Conclusion memoryfixer:

Again with Core...
module = {
    name: "MemoryFixer",
    author: "CzechHek",
    onUpdate: function () {
        timer.hasTimePassed(3000) && (Runtime.gc(), timer.reset());
    }
}

script.import("Core.lib");
timer = new MSTimer();
Runtime = Java.type("java.lang.Runtime").getRuntime();
flexing one line code script using core ^

how many times did this guy flex core

ChocoPie_isme

@Conclusion said in Optimization and LiquidBounce:

@ChocoPie_isme said in Optimization and LiquidBounce:
@CzechHek said in Optimization and LiquidBounce:
@idiot said in Optimization and LiquidBounce:

@Conclusion memoryfixer:

Again with Core...
module = {
    name: "MemoryFixer",
    author: "CzechHek",
    onUpdate: function () {
        timer.hasTimePassed(3000) && (Runtime.gc(), timer.reset());
    }
}

script.import("Core.lib");
timer = new MSTimer();
Runtime = Java.type("java.lang.Runtime").getRuntime();
flexing one line code script using core ^
how many times did this guy flex core

69420 times

yorik100

Never had any problems

WYSI

~~After all, it worked well. My Ram usage went from 1.1GB to~~
~~200mb (I'm scared). Maybe because of my ram cleaner, and~~
~~memoryfix code. Btw I had to uninstall my ram cleaner. It causes this problem.~~
(after a while it went up to 500mb and 1.4gb my computer broken)

Azure

i love how czechhek always flexes about his one-liner abilities

WYSI

@Azure said in Optimization and LiquidBounce:

i love how czechhek always flexes about his one-liner abilities

flexing is ~~good but~~ bad tho

Senk Ju

One shouldn't be proud of writing such code. It's pretty bad.