-
Notifications
You must be signed in to change notification settings - Fork 649
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.
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
test-4.0.3 witness_node CPU 100% #2078
Comments
Thread 18 looks like gdb has a problem with boost's context - the stack of that A possible cause in thread 1 is an apparent missing initialization in Next time you see this, please use |
I think I was wrong, the |
Note that 100% (or more) CPU can be normal during syncing. In testnet in particular, during the load-test blocks, there is no visible syncing progress with high CPU load. At which block did that happen? |
It's thread 1.
It's a node which is in sync already. To reproduce the issue, restart a synced node, check after the time passed |
Thanks. I think what happens is that Reproducability depends on log settings. |
Was able to reproduce the problem with log-level warn and a short rotation interval. At the interval, CPU usage jumps up to 100% until the next message is logged, as expected. |
@pmconrad - what was the rotation intervals under which this was caused ? |
It's independent from the rotation interval, I just used a low interval for easier testing (didn't want to wait for an hour each time). |
Bug Description
After started witness_node for a while, its CPU went to 100% .
From my stack backtrace, it seems it's either related to log rotation (thread 1) or task switching (thread 18, seems potentially a stack overflow), or both. Note: after interrupted the process in gdb then continued, thread 18 became normal.
Thanks to @syalon for reporting.
Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.
Steps To Reproduce
Restart witness_node, then wait.
Host Environment
Please provide details about the host environment. Much of this information can be found running:
witness_node --version
.CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: