draw_ram_indicator() easier numbers to read, includes RAM just collected #452
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The idea here was twofold:
Since there will be loops that absolutely require gc.collect(), perhaps we can make a habit of doing it like:
...so that we can at least see how much memory had been used and that gc.collect() freed it for x times for this routine? Otherwise, a bad habit of collecting memory even when it's not necessary may become the norm?
Alternately, I wonder if we might never gc.collect() except where we are absolutely sure it's necessary... and then more generally use try/except "MemoryError", then do gc.collect() within the except block, and continuing on?
What is the purpose of this pull request?
Debugging RAM usage.