Page MenuHomePhabricator

Fix a slow memory leak in long-lived FutureIterator objects, as used by FuturePool
ClosedPublic

Authored by epriestley on Sep 17 2020, 7:52 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jan 25 2024, 2:25 AM
Unknown Object (File)
Jan 20 2024, 4:41 PM
Unknown Object (File)
Jan 16 2024, 10:59 PM
Unknown Object (File)
Jan 16 2024, 5:13 PM
Unknown Object (File)
Jan 12 2024, 5:16 PM
Unknown Object (File)
Jan 1 2024, 4:31 PM
Unknown Object (File)
Dec 28 2023, 4:49 PM
Unknown Object (File)
Dec 27 2023, 1:37 PM
Subscribers
None

Details

Summary

See T13572. FutureIterator does not release futures, so long-lived iterators (like the one that FuturePool may build) can end up leaking memory.

This affects the FuturePool used by the daemon overseer.

See T13572 for more discussion.

Test Plan
  • Ran the simple FutureIterator script from T13572. Before: memory held during iteration, script grows without bound. After: memory released, script uses stable memory.
  • Ran the overseer with memory logging and an immediate wakeup from hibernation. Before: saw memory usage grow without bound at a rate of ~300MB/day. After: saw memory usage stable.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable