netblue30 / firetools

Firejail GUI
GNU General Public License v2.0
212 stars 32 forks source link

Firetools fstats v0.9.58 cpu% goes high for systemd > 242.85-2. #45

Open kdemeoz opened 4 years ago

kdemeoz commented 4 years ago

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.

  1. For all systemd versions tested so far above 242.85-2, running applications in Firejail continues to provide normal behaviour, but then viewing them in the Firetools fstats window immediately drives up overall cpu% high, due to high cpu% by fstats.
  2. The problem is repeatable by independent users [see Manjaro thread for other users' confirmations], & is independent of Desktop Environment [KDE, Cinnamon, Xfce tested, at least], & independent of distros [at least, for Arch-based ones; Manjaro & EndeavourOS tested].
  3. No Firetools fstats problem occurs for systemd versions 242.85-2 (& below), however given current Arch versions are already higher than that, this is an ongoing problem.
  4. A temporary workaround is available; downgrade installed systemd version back to 242.85-2 or lower.
  5. My original Manjaro test https://forum.manjaro.org/t/nasty-fstats-cpu-bug-since-testing-update-2019-09-06/102009?u=kdemeoz
  6. My EndeavourOS test https://forum.manjaro.org/t/nasty-fstats-cpu-bug-since-testing-update-2019-09-06/102009/24?u=kdemeoz
kdemeoz commented 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.

netblue30 commented 4 years ago

I still cannot reproduce it. It could be a systemd problem. I'll keep an eye on it, thanks.

kdemeoz commented 4 years ago

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.