[Users] [Bug 3145] Crash due to memory leak

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Sat Apr 19 11:57:46 CEST 2014


--- Comment #1 from Michael Schwendt <mschwendt at gmail.com> ---
What makes you think it's a "memory leak"?

The backtrace (a crash in glibc memory management) looks very much like heap
corruption caused by an earlier interruption of the IMAP session, which has
been plagueing Claws Mail for a very long time (
https://bugzilla.redhat.com/1070480#c5 ). As such, the backtrace is rather
useless because it doesn't tell what code had corrupted the memory prior to
calling malloc.

#7  0x4806b52a in g_malloc0 (n_bytes=n_bytes at entry=4336) at gmem.c:134
#8  0x080e5ab2 in imap_session_new (account=0x86e84e8, folder=0x871cf20) at

You are receiving this mail because:
You are the assignee for the bug.

More information about the Users mailing list