You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @dobin. I appreciate raising the bug. I have a wild guess that excessive CPU utilization could be triggered by a tight loop happening under unpredictable conditions.
Can I kindly ask for CPU profiles?
You'll need Go 1.23.x installed on the machine. Then run the following command when Fibratus is stuck in a high CPU consumption state:
go tool pprof http://localhost:8482/debug/pprof/profile
After the command completes, you'll land into pprof CLI. Then type proto and attach the pb.tgz file.
Additionally, could you also get the following by opening the URL in the browser?
Activity
rabbitstack commentedon Jan 20, 2026
Hi @dobin. I appreciate raising the bug. I have a wild guess that excessive CPU utilization could be triggered by a tight loop happening under unpredictable conditions.
Can I kindly ask for CPU profiles?
You'll need
Go 1.23.xinstalled on the machine. Then run the following command when Fibratus is stuck in a high CPU consumption state:After the command completes, you'll land into pprof CLI. Then type
protoand attach thepb.tgzfile.Additionally, could you also get the following by opening the URL in the browser?
Lastly, any warning/error logs, or if you notice excessive log messages being written.
Thanks
P.S. I'm currently sick, so I'll not be able to look into it immediately.
dobin commentedon Jan 23, 2026
profile001.pb.gz
debug-vars.json
fibratus.log
goroutine.txt
System Boot Time: 20.01.2026, 11:05:52
rabbitstack commentedon Jan 23, 2026
Thanks for providing these files. I narrowed it down to an infinite loop which also causes a deadlock. I'll correct this defect in the next version.