Database query garbage collector unintentionally drops query listeners that are still active
The query garbage collector (QueryCollectorImpl
) does not ensure that the rather newly introduced QueryListening
class (#450 (closed)) has actually flushed (performed) all of the queued-up listener registrations before starting to collect queries.
This can result in accidentally dropped listeners that are still alive and should be left as is.
This seems to be at least one major cause of recently accumulated database problems that have started to annoy and drive developers away from the master version.
Huge thank you to @reino for finding this out - super quickly I might add!