Devart Forums

Delphi 2009, MyDAC 570

Memory leaks are reported by the memory manager when MyDump is used to create an SQL dump with a MyEmbedded connection. No problem with MyConnection. No problem if MyDump is configured with objects set to false (tables, data, etc.).

Below is the text from the Application Error message:

Exception EAccessViolation in module libmysqld.dll at 001D2DF3
Access violation at address 101D2DF3 in module ‘libmysqld.dll’. Read of address FEEEFFFA.

Unexpected small memory leaks message:

13-20 bytes: Unicodstring x 23
21-28 bytes: Unicodstring x 12
29-36 bytes: Unicodstring x 10
37-44 bytes: Unicodstring x 5
45-52 bytes: Unicodstring x 9
53-60 bytes: Unicodstring x 9
61-68 bytes: Unicodstring x 2
69-76 bytes: Unicodstring x 3, Unknown x 1
77-84 bytes: Unicodstring x 2
85-92 bytes: Unicodstring x 1
93-100 bytes: Unicodstring x 2
269-284 bytes: TMutex x 1, TMySQLAPIEmbedded x 1
797-976 bytes: Unknown x 1

Thank you for your assistance - once again.

I could not reproduce the problem. Please send me a complete sample at dmitryg*devart*com to demonstrate it, including a script to create and fill table.
Also supply me the exact version of your Embedded server.

Dimon,

The problem seems to be solved. It appears to have been data related.

I made a demo but couldn't reproduce the leak. Then I trimmed down the problem application until it was similar to the demo - but it always leaked.

The only difference between the two was that they used different database folders. Dropping the original database and recreating it stopped the memory leak reports. Both were created using MySQL community 5.1.30 GA.

Thank you for you assistance.

It is good to see that this problem has been solved.