Hi all, Having watched the SOGo daemon repeatedly chomp through all of the RAM and swap on my server while syncing a large calendar over ActiveSync, I believe I have discovered the cause.
It's an unconstrained use of the auto-release pool in the method 'processSyncCommands' (file SOGoActiveSyncDispatcher+Sync.m). By adding a locally controlled auto-release pool to the inner 'for' loop in this function, the memory consumption of the daemon during the same ActiveSync calendar synchronisation stays within 50K or so. Much saner than the multi-gigabytes it was consuming before. I'd like to offer this minor change back for incorporation into future releases. What is the etiquette for doing so? Should I post the patch details to this mailing list? -- [email protected] https://inverse.ca/sogo/lists
