Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
complete --wraps can cause a background thread to burn CPU #5638
I happened upon a fish process using "300%" CPU that was still interactive, when working on the
A thread is going nuts trying to walk the wrap chain.
referenced this issue
Feb 12, 2019
He... "sudo -s -s -E"".
And the underlying cause should be fairly similar -
Similarly, in @floam's example you need both wrap calls. So I'd imagine one wraps the other, so it ping-pongs from one to the other and back again.