Devart Forums

We just moved from IBDAC version 5.7.27 to 6.0.1 because of Delphi Tokyo and now we are getting following memory leaks here and there, any idea why? This didn't happen in version 5.7.27.

--------------------------------2017/5/9 13:32:26--------------------------------
A memory block has been leaked. The size is: 68

This block was allocated by thread 0x1918, and the stack trace (return addresses) at the time was:
407642
883450 [CLRClasses.pas][CLRClasses][CLRClasses.Marshal.AllocHGlobal][445]
991265 [IBCClasses.pas][IBCClasses][IBCClasses.TGDSTransaction.GetMultiTransactionID][3308]
945BB7 [DBAccess.pas][DBAccess][DBAccess.TDBAccessUtils.GetMultiTransactionID][17243]
95410B [DASQLMonitor.pas][DASQLMonitor][DASQLMonitor.TCustomDASQLMonitor.InternalTRCommit][863]
952475 [DASQLMonitor.pas][DASQLMonitor][DASQLMonitor.TCustomDASQLMonitor.TRCommit][352]
949234 [DBAccess.pas][DBAccess][DBAccess.TDATransaction.Commit][18241]
9C23FF [IBC.pas][IBC][IBC.TIBCTransaction.Commit][3045]
...

The block is currently used for an object of class: Unknown

The allocation number is: 162031

Current memory dump of 256 bytes starting at pointer address 7F816D10:
04 04 00 33 10 00 00 01 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
EA 22 3B 75 80 80 80 80 00 00 00 00 A1 8A 81 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B7 79 02 00 42 76 40 00 8B A6 40 00 AA AE 40 00 DE F0 94 00 DF 07 95 00 D1 57 95 00 ED 39 95 00
1C 23 95 00 D3 EF 93 00 4E EE 93 00 A5 18 2D 01 18 19 00 00 A8 25 00 00 5E 76 40 00 A9 A6 40 00
F5 AE 40 00 16 A8 40 00 23 A8 40 00 C8 0B 95 00 68 ED 4D 00 F6 C5 40 00 C4 62 37 75 D9 0F 7C 77
A4 0F 7C 77 44 00 00 00 2C E2 94 00 B7 D5 AF EC 70 CC 60 01 80 80 80 80 80 80 80 80 80 80 80 80
80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
. . . 3 . . . . € € € € € € € € € € € € € € € € € € € € € € € €
€ € € € € € € € € € € € € € € € € € € € € € € € € € € € € € € €
ê " ; u € € € € . . . . ¡ Š   . . . . . . . . . . . . . . . .
· y . . B v @ . ‹ ¦ @ . ª ® @ . Þ ð ” . ß . • . Ñ W • . í 9 • .
. # • . Ó ï “ . N î “ . ¥ . - . . . . . ¨ % . . ^ v @ . © ¦ @ .
õ ® @ . . ¨ @ . # ¨ @ . È . • . h í M . ö Å @ . Ä b 7 u Ù . | w
¤ . | w D . . . , â ” . · Õ ¯ ì p Ì ` . € € € € € € € € € € € €
€ € € € € € € € € € € € € € € € € € € € € € € € € € € € € € € €

FYI: If we remove SQLMonitor component from our datamodule, this leak is gone.

Thank you for the information. We have reproduced and fixed the issue. This fix will be included in the next build of IBDAC.