This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Deadlock in logging.config.dictConfig
Type: Stage:
Components: Library (Lib) Versions: Python 3.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: mrc
Priority: normal Keywords:

Created on 2020-04-23 07:19 by mrc, last changed 2022-04-11 14:59 by admin.

Files
File name Uploaded Description Edit
deadlock_logging.log mrc, 2020-04-23 07:19 The thread tracebacks
Messages (1)
msg367085 - (view) Author: (mrc) Date: 2020-04-23 07:19
DataGraham in #django reported a deadlock with a very specific logging configuration. Issue is reproducible from this code: https://github.com/data-graham/wedge. To trigger the deadlock at least one handle must be enable. Note how there there are no loggers using those handlers. (https://github.com/data-graham/wedge/blob/master/wedge/settings.py#L127-L169)

The two offending locks causing the deadlock are logging._lock and a lock used by importlib._bootstrap._imp (_PyImport_AcquireLock).


TH1> start and complete the logging configuration via dictConfig. An handler is configured but no logger uses it, only a weakref holds it
TH2> start logging configuration, acquires logging._lock
TH1> import some module, acquiring the import lock
TH1> the garbage collector starts and reclaims the unused handled (only a weakref exists)
TH1> the weakref callback tries to acquire logging._lock. WAITING
TH2> start importing some module, try to acquire import lock. DEADLOCK

Attached the traceback of the threads. I could test this with Python3.7 only (and Django 3.0).
History
Date User Action Args
2022-04-11 14:59:29adminsetgithub: 84551
2020-04-23 07:19:46mrccreate