This only applies to 0.4.7.x. Even though we worked on https://gitlab.torproject.org/tpo/core/tor/-/issues/40527, it appears that a second call from the DNS subsystem triggering the general overload timeout was forgotten/missed. The problem lies in the libevent DNS callback.