Open japc opened 5 months ago
At spamhaus we noticed the memory loss too, and traced it to the rspamd_regexp plugin. We are busy making a workaround without the regexp plugin that still preserves practically all functionality. Hope to have a solution in a few days. Thanks for the detailed bug report, and for raising the rspamd issue!
The regexp issue got a workaround, and we've rewritten the leaky cryptowallet match code. Should be fixed now, our own testing no longer shows memory loss issues.
Thank you.
There was also a rspamd problem with the regex code that was promptly fixed (issue linked).
There was also a rspamd problem with the regex code that was promptly fixed (issue linked).
Yes, I've seen it. In fact the current release mentions that issue because it still uses PCRE but the regexes should be safe to use even for rspamd versions that still contain the bug.
Thank YOU very much for your excellent debugging work, finding an example URL that triggered the issue and the point in the code where it went wrong!
Hi,
Have had an increase of memory consumption with SPAMHAUS_HBL_URL enabled. Usually the rspamd normal processes take 100MB to 400MB but with SPAMHAUS_HBL_URL on there are some consuming about 3GB.
Tried in a couple of servers:
with SPAMHAUS_HBL_URL enabled on both, both have the huge mem processes with SPAMHAUS_HBL_URL only on one of them, only that will have the huge mem processes
Straced the rspamd workers since the rspamd start and I can see an increasing memory allocation:
And, although from the trace the memory appears to be unmapped, it is still allocated by the process:
The mem not being allocated may be a different problem, but there seems to be something weird going on on the url algo table processing.