From 822cb39dfa277d6ef27233ac7f5c3dcd2562bb14 Mon Sep 17 00:00:00 2001 From: Mark Haines Date: Fri, 30 Dec 2016 11:05:37 +0000 Subject: [PATCH] Use the new twisted logging framework. Hopefully adding an observer to the new framework will avoid a memory leak https://twistedmatrix.com/trac/ticket/8164 --- synapse/config/logger.py | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/synapse/config/logger.py b/synapse/config/logger.py index ec72c9543..63e69a7e0 100644 --- a/synapse/config/logger.py +++ b/synapse/config/logger.py @@ -15,7 +15,7 @@ from ._base import Config from synapse.util.logcontext import LoggingContextFilter -from twisted.python.log import PythonLoggingObserver +from twisted.logger import globalLogBeginner, STDLibLogObserver import logging import logging.config import yaml @@ -180,5 +180,15 @@ def setup_logging(log_config=None, log_file=None, verbosity=None): with open(log_config, 'r') as f: logging.config.dictConfig(yaml.load(f)) - observer = PythonLoggingObserver() - observer.start() + # It's critical to point twisted's internal logging somewhere, otherwise it + # stacks up and leaks kup to 64K object; + # see: https://twistedmatrix.com/trac/ticket/8164 + # + # Routing to the python logging framework could be a performance problem if + # the handlers blocked for a long time as python.logging is a blocking API + # see https://twistedmatrix.com/documents/current/core/howto/logger.html + # filed as https://github.com/matrix-org/synapse/issues/1727 + # + # However this may not be too much of a problem if we are just writing to a file. + observer = STDLibLogObserver() + globalLogBeginner.beginLoggingTo([observer])