Icedove creates a very large number of child threads and does not
appear to clean them up sensibly.  Performance degrades in
long-running instances.  Could potentially lead to situations where
system becomes inaccessible to a user running Icedove if max processes
is exhausted.

Attached gdb thread backtrace of instance which as been running for
about one week and has over 600 children.

See also https://bugzilla.redhat.com/show_bug.cgi?id=805961 (same bug
in another distro)
and https://bugzilla.mozilla.org/show_bug.cgi?id=745212 (same/similar
bug in another OS)

Duncan,

Do you still see this problem when using a current version of icedove?

Hello Wayne,
addressed only the bug itself (683264@bugs.debian.org) only the bug
report will get your message. Even the original reporter wont get a
email as I'm not wrong.

Only people that have explicitly subscribed to the bug or more generally
to the Icedove source package will get a information in CC.

So, to get Duncan asked you will need him addressed in To or Cc also,
like I've done now.

BTW: Thanks for watching into the bug reports on Debian! Really appreciated.