Repository navigation
fix: memory growing by gigabytes over days - #117
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tidegauge 0.6.0 reached a 3.2 GB footprint after five days on one Mac.
heapshowed ~4.0M NSRunningApplication, ~4.0M NSLock, ~4.2M NSURL, ~7.0M CFString and ~296k CWFRequestParameters objects: the sampler (and the sensor and disk workers) call AppKit/LaunchServices/CoreWLAN from their own threads, which have no autorelease pool, so every autoreleased object returned during a pass was kept forever.Fix: wrap each sampler pass, each sensor read, and the disk inventory/IO reads in
objc2::rc::autoreleasepool.Verified (release builds side by side, hidden, separate HOME, 5 minutes):
cargo testandTIDEGAUGE_TEST_LANG=nb cargo testpass.