A NOTE has been added to this issue. ====================================================================== http://www.dbmail.org/mantis/view.php?id=738 ====================================================================== Reported By: niki Assigned To: ====================================================================== Project: DBMail Issue ID: 738 Category: IMAP daemon Reproducibility: always Severity: crash Priority: normal Status: new target: ====================================================================== Date Submitted: 22-Nov-08 12:15 CET Last Modified: 22-Nov-08 21:02 CET ====================================================================== Summary: Memory leak resulting in crash Description: I noticed that imapd was continuing using more and more memory after I suddenly lost connection with it.
Tried to run it with gdb to get a backtrace of the crash, but there was no stack for gdb. So I have now run a memory check on it with walgrind and it shows some memory leaks. ====================================================================== ---------------------------------------------------------------------- niki - 22-Nov-08 14:23 ---------------------------------------------------------------------- Running it with debugging libs didn't provide any more info, but I now have a 2nd memcheck log, and a dbmail.err file with loglevel 128 now (159MB in size) that I can put up for download if you are interested. What I have from gdb is this: (gdb) run -D -f /etc/dbmail/dbmail.conf -p /var/run/dbmail-imapd.pid Starting program: /usr/sbin/dbmail-imapd -D -f /etc/dbmail/dbmail.conf -p /var/run/dbmail-imapd.pid [Thread debugging using libthread_db enabled] [New Thread 0xb74ca6d0 (LWP 25348)] [New Thread 0xb74b8b90 (LWP 25351)] [New Thread 0xb6cb7b90 (LWP 25352)] [New Thread 0xb64b6b90 (LWP 25353)] [New Thread 0xb5cb5b90 (LWP 25354)] [New Thread 0xb54b4b90 (LWP 25355)] [New Thread 0xb4cb3b90 (LWP 25356)] [New Thread 0xb44b2b90 (LWP 25357)] [New Thread 0xb3cb1b90 (LWP 25358)] [New Thread 0xb34b0b90 (LWP 25359)] [New Thread 0xb2cafb90 (LWP 25360)] [Thread 0xb2cafb90 (LWP 25360) exited] [Thread 0xb44b2b90 (LWP 25357) exited] [Thread 0xb64b6b90 (LWP 25353) exited] [Thread 0xb6cb7b90 (LWP 25352) exited] [Thread 0xb4cb3b90 (LWP 25356) exited] [Thread 0xb5cb5b90 (LWP 25354) exited] [Thread 0xb54b4b90 (LWP 25355) exited] [Thread 0xb3cb1b90 (LWP 25358) exited] Program exited with code 0113. (gdb) bt No stack. (gdb) I get the same both with or without the "-D" option. ---------------------------------------------------------------------- paul - 22-Nov-08 21:02 ---------------------------------------------------------------------- exit 113 is a known problem. Please test http://git.dbmail.eu/?p=paul/dbmail;a=commitdiff;h=fedf0b62c696bcd383619725c290702f7f63b5d6 which should fix this. This is all most likely unrelated to the memory leakage, but g_slice leakage is unreliable unless you run valgrind with G_SLICE=always-malloc valgrind --leak-check=full Issue History Date Modified Username Field Change ====================================================================== 22-Nov-08 12:15 niki New Issue 22-Nov-08 12:15 niki File Added: imapd-1.memcheck.bz2 22-Nov-08 14:23 niki Note Added: 0002650 22-Nov-08 21:02 paul Note Added: 0002651 ====================================================================== _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
