High CPU usage compared to old version

[CodingPhyshhh]

High CPU usage

Issue:

• Idle CPU usage of 17.0.0 is significantly higher comparing to 13.0.3.

  • fabricloader0.19.1-1.21.11 with modmenu17.0.0
    latest_1.21.11_modmenu17.0.0.log
    

  • fabricloader0.19.1-1.21.11 only
    latest_1.21.11.log
    

  • fabricloader0.16.14-1.21.4 with modmenu13.0.3
    latest_1.21.4_modmenu13.0.3.log
    

  • fabricloader0.16.14-1.21.4 only
    latest_1.21.4.log
    

[AV306]

+1; Mod Menu causes consistent 100% usage of a single CPU core on my machine (Intel Core i5-10400), even when not in a world.

[gniftygnome]

Could one of you who are reporting this try turning off the update checker and see if it resolves the issue? Also, any chance you don't have an Internet connection when playing, or maybe it's firewalled and your system can't access modrinth.com?

[CodingPhyshhh]

Could one of you who are reporting this try turning off the update checker and see if it resolves the issue?

Yes. Turning off the update checker resolve the issue (after restarting Minecraft).

Also, any chance you don't have an Internet connection when playing, or maybe it's firewalled and your system can't access modrinth.com?

For additional information, internet is always connected. I don't know how to test the modrinth.com accessibility from Minecraft, but issue still present after I temporary disable the firewall (these are done with update checker enabled). Also, I can access modrinth.com form browser without any trouble.

[gniftygnome]

@CodingPhyshhh

OK, good to know. Would you also be willing to try ModMenu in 26.1.x and see if the problem is still there? That release has a bunch of changes to the update checking. If the problem is resolved there, then I need to backport the changes to the 1.21.x versions.

[gniftygnome]

I've been unable to reproduce this problem. This means I can't tell what versions it applies to and what versions are unaffected, and if I try to fix it, I can't tell if it's fixed. So, it's pretty much stalled until something changes. The one thing I can do is try to backport the changes we've made in 26.1, but unless that turns out to be pretty easy to do, I may not get it done quickly. I'd like to have some confirmation 26.1 is fixed before putting in the effort.