[Swan-dev] Pluto memory consumption
D. Hugh Redelmeier
hugh at mimosa.com
Wed Mar 22 15:27:42 UTC 2017
| From: Andrew Cagney <andrew.cagney at gmail.com>
| On 21 March 2017 at 11:02, Paul Wouters <paul at nohats.ca> wrote:
| > That's because since we converted to libevent, we have no way of
| > listing these events to find them and delete them.
| Yea, they are global in the sense that they don't seem to be tied to a
| state, and reschedule themselves when they trigger:
Off the top of my head (I'm really short of time; sorry):
1) leaks of O(1) are of no consequence. There is only a small fixed
number of these events (I think) and so they are not a leak problem.
2) I think that there was a prefix in the name of an allocation that
meant that the leak detective should ignore it.
More information about the Swan-dev