mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3136] firejail --top causes single cpu core large load #1967
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1967
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Jan 9, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3136
Fedora 31 firejail 0.9.62 sourceforge RPM (installed with sudo dnf install ./firejail.rpm)
when starting firejail --top the first anomalous behavior observed is that the refresh is not smooth (it was on ubuntu 18 lts), it alternates between displaying the processes and displaying nothing, almost equal time for both. The column names are always displayed so it's not a terminal display issue probably.
It also causes a single CPU core to fluctuate from 100% to 50% in an almost sine wave.
@ghost commented on GitHub (Jan 9, 2020):
firejail --tree also causes a 100% single core spike before exiting. Though not sure if that one is expected. With watch -n1 grep something almost exact cpu behavior as --top