Open kdemeoz opened 4 years ago
It's disappointing to see no feedback on nor acknowledgement of this bug. It has not magicked itself away... continues to apply in [at least] Manjaro & Arch for all versions of systemd in the 243 & 244 series. My latest Manjaro mention: https://forum.manjaro.org/t/nasty-fstats-cpu-bug-since-testing-update-2019-09-06/102009/26?u=kdemeoz I hope that the next version of Firetools will solve this.
I still cannot reproduce it. It could be a systemd problem. I'll keep an eye on it, thanks.
Hello
Oh it definitely IS a systemd problem, but IMO they are unlikely to alter their latest code to suit Firetools, hence sadly i fear you will need to alter yours to suit their recent commit which caused this problem. Here's what a fellow Manjaroo found & advised me: https://forum.manjaro.org/t/nasty-fstats-cpu-bug-since-testing-update-2019-09-06/102009/27?u=kdemeoz
FYI, this modified launcher is a completely successful workaround; this way ALL the high cpu% misbehaviour vanishes: sudo sysctl -w kernel.pid_max=32768 && /usr/lib/firetools/fstats
Regards, Kadee.
Sent from ProtonMail, encrypted email based in Switzerland.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, 21 December 2019 11:34, netblue30 notifications@github.com wrote:
I still cannot reproduce it. It could be a systemd problem. I'll keep an eye on it, thanks.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
For full details, testing & discussion pls see my Manjaro Forum thread https://forum.manjaro.org/t/nasty-fstats-cpu-bug-since-testing-update-2019-09-06/102009.
Summary.