Memory Leak in TIdSMTP

Giganews Newsgroups
Subject: Memory Leak in TIdSMTP
Posted by:  Thomas Zangl (usen…@tzis.net)
Date: Mon, 20 Dec 2004

Hi,

I noticed a memory leak in TIdSMTP:
(Testcase: Sending a simple email, no attachments, single recipient)

MemCheck version 2.70

Total leak: 40 bytes

*** MEMCHK: Blocks STILL allocated ***

Leak #0 Instance of TIdSMTPEnhancedCode
    Size: 20
    1 Occurence
    call stack - 0 : (no debug info) Find error: 005F24AA
    call stack - 1 : (no debug info) Find error: 0057FB18
    call stack - 2 : (no debug info) Find error: 005F24EA
    call stack - 3 : (no debug info) Find error: 005869F2
    call stack - 4 : (no debug info) Find error: 0058D445
    call stack - 5 : (no debug info) Find error: 0058FD59
    call stack - 6 : (no debug info) Find error: 005F2CE1
    call stack - 7 : (no debug info) Find error: 005F3B95
    call stack - 8 : (no debug info) Find error: 00569DF5
    call stack - 9 : (no debug info) Find error: 00569DB1
    call stack - 10 : (no debug info) Find error: 005FEFA3
    call stack - 11 : (no debug info) Find error: 006A8EC4
    call stack - 12 : (no debug info) Find error: 006A9D52
    call stack - 13 : (no debug info) Find error: 006A9328
    call stack - 14 : (no debug info) Find error: 006AA619
    call stack - 15 : (no debug info) Find error: 00428F1B
    call stack - 16 : (no debug info) Find error: 0040519A
    call stack - 17 : (no debug info) Find error: 7C57B384
    call stack - 18 : (no debug info) Find error: FFFFFFFC

Leak #1 Instance of TIdSMTPEnhancedCode
    Size: 20
    1 Occurence
    call stack - 0 : (no debug info) Find error: 005F24AA
    call stack - 1 : (no debug info) Find error: 0057FB18
    call stack - 2 : (no debug info) Find error: 005F24EA
    call stack - 3 : (no debug info) Find error: 005869E0
    call stack - 4 : (no debug info) Find error: 0058D445
    call stack - 5 : (no debug info) Find error: 0058FD59
    call stack - 6 : (no debug info) Find error: 005F2CE1
    call stack - 7 : (no debug info) Find error: 005F3B95
    call stack - 8 : (no debug info) Find error: 00569DF5
    call stack - 9 : (no debug info) Find error: 00569DB1
    call stack - 10 : (no debug info) Find error: 005FEFA3
    call stack - 11 : (no debug info) Find error: 006A8EC4
    call stack - 12 : (no debug info) Find error: 006A9D52
    call stack - 13 : (no debug info) Find error: 006A9328
    call stack - 14 : (no debug info) Find error: 006AA619
    call stack - 15 : (no debug info) Find error: 00428F1B
    call stack - 16 : (no debug info) Find error: 0040519A
    call stack - 17 : (no debug info) Find error: 7C57B384
    call stack - 18 : (no debug info) Find error: FFFFFFFC

*** MEMCHK: End of allocated blocks ***

*** MEMCHK: Chronological leak information ***

* Instance of TIdSMTPEnhancedCode (Leak #1) Size: 20
* Instance of TIdSMTPEnhancedCode (Leak #0) Size: 20

*** MEMCHK: End of chronological leak information ***

*** MEMCHK: Blocks written to after destruction ***

    Bad blocks count: 0

*** MEMCHK: End of blocks written to after destruction ***

Please consider using MemCheck to test your components. I tried to find
the leak but to no avail. Indy´s source is far too complex for my
limited time...

Best regards,

--
----------------------------------------------------------------
,yours Thomas Zangl -thom…@tzi.dhs.org- -TZ1-6BONE-
http://tzi.dhs.org -http://www.borg-kindberg.ac.at
Use YAMC! now! Get it athttp://www.borg-kindberg.ac.at/yamc/

Replies