Page MenuHomePhabricator

User reporting unbounded memory usage by TriggerDaemon
Closed, WontfixPublic

Description

See IRC. Initial probing didn't give me much to go on.

The --trace-memory flag is no longer very reasonable to pass to the daemons manually, so the next reasonable step would be to surface it from phd or possibly imply it for phd debug.

While I'm in there, I'd kind of like to get rid of the verbose flag and just have the daemons emit log messages into the service profiler so that "--trace" activates logging.

Event Timeline

epriestley raised the priority of this task from to Normal.
epriestley updated the task description. (Show Details)
epriestley added a project: Daemons.
epriestley added a subscriber: epriestley.
epriestley claimed this task.

I fixed the totally unrelated half of this (bad default verbosity of phd debug) at some point in the recent-ish few months.

We haven't seen other memory issues in more than a year and I have no idea what the original repro was for this.

¯\_(ツ)_/¯