JAVA CPU Lag

[Frostworkaeon]

I have a serious problem where when i load into a game i get terrible lag. at times players have claimed that there is '1500 ping' on me, but when I have checked the ping looks fine but what doesnt look fine is Java, which is using up to 60% of my cpu. I went thru the trouble to get the older versions of java and so far i have tried java 10, but the problem still exists. I know im not the only one whos had this problem, is there a solution? i switched to python client faf at somebodys advice but the issue persists as whatever uses java still uses java. this is a bummer. thanks for any help. diagnosing requires me to somewhat ruin others games and tinker with task manager while they sit with lag, but i guess i could do it again if i need to.. ugh

[Geosearchef]

This is known, fixing it isn't as trivial though.

If you close everything related to java client, do you still encounter that issue? The ice adapter shouldn't use a lot of cpu.

[Frostworkaeon]

when i close java thru task manager then i believe either the client or the supcom closes, i cant remember, its either one or both. i can check if i should, should I? I did have this issue once before, and i cant remember how i straightened it out, i think i might have switched operating systems to fix it. .....

[Rikai]

According to my experience, you can safely shutdown the "downlords faf client" via task manager while ingame without losing connection, HOWEVER you cannot shut it down normally by clicking the X at the upper right corner, because then your WOULD lose connection ingame. (Closing it normally kills the ice adapter as well)

The 95% CPU usage bug has persisted for me for a long time now, about once a day, even with the newest "RC-10" and is one of two main reasons why I switched to Python client for most of the time. (The other one being that I cannot watch replays while lobbysimming when on java client, and i can while on python)
The other reasons are just of cosmetic nature for me.

[Rikai]

There is a new Java client Released (RC11) (and almost immediately after that, the official "v1.0.0" client was released too).

axel12 is quite sure to have fixed the CPU bug. Let's hope his work on the client has paid off.