Stderr backtrace caused by redis.client.Redis.__del__ on process exit.

[byron-lambda]

Version: 5.0.1

Platform: Python 3.8.18 on Ubuntu 20.04

Description: Backtrace to stderr on process exit due to redis.client.Redis.__del__()

Here is the trace:

Exception ignored in: <function Redis.__del__ at 0x7fcf29e50ca0>
Traceback (most recent call last):
  File "/venv/lib/python3.8/site-packages/redis/client.py", line 491, in __del__
  File "/venv/lib/python3.8/site-packages/redis/client.py", line 506, in close
  File "/venv/lib/python3.8/site-packages/redis/connection.py", line 1155, in disconnect
  File "/venv/lib/python3.8/site-packages/redis/connection.py", line 1062, in _checkpid
AttributeError: 'NoneType' object has no attribute 'getpid'

Occurs due to unloaded globals being referenced in methods called in destructors on process exit. See warning in Python docs here

This can be fixed in a couple of ways:

1. Add an exception handler to redis.client.Redis.__del__() as it appears has been done in many other destructors (

   redis-py/redis/connection.py

   Line 226 in d3a3ada

   def __del__(self):

   for example)
2. Add references to required globals to the redis.connection.ConnectionPool class and call via the references. The globals that require references in are os.getpid and chain (from itertools) afaict.

NOTE: It is quite hard to come up with a small piece of code to reproduce this issue as it is caused by a race in the unload order at exit. I'll try to come up with something reliable if req'd.

NOTE: The issue is triggered by

redis-py/redis/client.py

Line 506 in d3a3ada

self.connection_pool.disconnect()

which was recently introduced in 012f7cf

[diogosilva30]

Can confirm this behaviour with version 5.0.1 with Django. I get this error when the development server restarts

[Alucido]

Can confirm this behaviour with version 5.0.8, Python 3.9, when running pytest test suite opening a Redis Client in a subclass of the beam.DoFn class, as part of its setup method. The error is reproduced when the test suite ends and the client is closed.

[noirbee]

I've opened #3397 after encountering this issue following a ddtrace update (probably due to the module loading / patching shenanigans it performs for libraries it wants to monkey-patch).

Thanks @byron-lambda for opening this issue in the first place, and pointing me in the right direction !