Our monitoring shows that seantis.dir.events might be suffering from a memory leak. See the memory/swap statistics of the last seven days (prior to which I issued a restart).
We don't have this problem with other modules - this is the only one. So it's either a dependency or seantis.dir.events itself that's causing this issue.
Our monitoring shows that seantis.dir.events might be suffering from a memory leak. See the memory/swap statistics of the last seven days (prior to which I issued a restart).
We don't have this problem with other modules - this is the only one. So it's either a dependency or seantis.dir.events itself that's causing this issue.