I did some further tests and could narrow down to a problem with remote logging and a non-existing FQDN. Removing the erroneous entry stops the continuous increase of memory.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
