We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
When running with 100s of bars (most of which "complete" and stop being updated), memory begins to climb. This behaviour remains even if I Abort my Bars.
There's a corresponding increase in CPU use too,
Thanks for the cool library.
The text was updated successfully, but these errors were encountered:
Thanks for reporting! I think I know why is that.
Sorry, something went wrong.
address issue #115
Can you please test with head master? Should be fixed.
Just for reference, the bug introduced in 11d342b. It appears only when bars don't fit to terminal, i.e. number of bars are greater than terminal height.
minor: var refactoring
minor: wg.Wait err branch
minor: if local var
I'm not sure I can test this now, I've switched to another library for the progress bars and they're deeply integrated into some other changes.
I went back and tried it against master. I cannot reproduce either the memory or CPU problems anymore!
No branches or pull requests