8000 High CPU usage (possible deadlock) · Issue #6 · secureworks/dcept · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

High CPU usage (possible deadlock) #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
vlakas opened this issue Jul 29, 2017 · 1 comment
Open

High CPU usage (possible deadlock) #6

vlakas opened this issue Jul 29, 2017 · 1 comment

Comments

@vlakas
Copy link
vlakas commented Jul 29, 2017

High CPU usage has been noticed with dcept in docker (master branch). dcep process consumes 100% of CPU core permanently.

root     22540  0.0  0.0  14776  2168 pts/2    S+   16:36   0:00 grep dcep
root     31237  0.0  0.0 155364 14896 ?        Ssl  Jun28   0:02 /usr/bin/docker start -a dcept
root     31261  0.0  0.0  20076  2812 pts/1    Ss+  Jun28   0:00 /bin/sh -c cron; /opt/dcept/dcept.py
root     31275 99.9  0.1 224028 24728 pts/1    Sl+  Jun28 45392:56 /usr/bin/python /opt/dcept/dcept.py

Here is strace of dcept process (with children).

dcept-deadlock.txt
@vlakas
Copy link
Author
vlakas commented Jul 29, 2017

Now I'm working on the following commit:

834a523

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vlakas
0