Page 1 of 1

Memory Leak

Posted: Mon 17 Oct 2011 09:26
by binfch
Hi there

Using FastMM4 I get a leak notice:

Code: Select all

--------------------------------2011/10/17 11:09:01--------------------------------
A memory block has been leaked. The size is: 12

This block was allocated by thread 0x1DD4, and the stack trace (return addresses) at the time was:
402B13 [system.pas][System][@GetMem][2447]
50230D [DB.pas][DB][TDataSet.GetBookmark][10494]
64501F [DALoader][TDALoader.LoadFromDataSet]
525A61 [DBAccess][TCustomDAConnection.SetConnected]
4FBDD6 [DB.pas][DB][TDataSource.SetDataSet][7558]
6531B9 [fServerForm.pas][fServerForm][TServerForm.FlushLogTables][1451]
6545E4 [UnitLogThread.pas][UnitLogThread][TLogThread.ExecuteSync][42]
431C34 [classes.pas][Classes][CheckSynchronize][9339]
489081 [Forms.pas][Forms][TApplication.WndProc][6670]
43425E [classes.pas][Classes][StdWndProc][10966]
767262FA [Unknown function at gapfnScSendMessage]

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

The allocation number is: 79284

Current memory dump of 256 bytes starting at pointer address 7EED1E68:
28 00 00 00 5D 76 E2 7E 01 00 00 00 97 29 4D 2B 00 00 00 00 89 F5 EC 7E 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 EA 38 01 00 13 2B 40 00 FB 3F 40 00 C2 43 40 00 30 40 40 00 2A A4 50 00
CD D2 50 00 81 5C 5C 00 62 49 50 00 51 D2 50 00 1E 69 5C 00 9F 2C 65 00 D4 1D 00 00 D4 1D 00 00
33 2B 40 00 19 40 40 00 0D 44 40 00 52 40 40 00 5F 40 40 00 EB A0 50 00 DE D2 50 00 44 4A 50 00
12 5D 5C 00 21 27 43 00 34 24 43 00 0C 00 00 00 80 38 50 00 04 D6 B5 85 94 FC 68 00 94 FF 68 00
94 FF 68 00 FB 29 4A 7A 00 00 00 00 61 17 ED 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
95 44 01 00 13 2B 40 00 FB 3F 40 00 C2 43 40 00 30 40 40 00 2A A4 50 00 CD D2 50 00 81 5C 5C 00
62 49 50 00 51 D2 50 00 1E 69 5C 00 EB 2E 65 00 D4 1D 00 00 D4 1D 00 00 33 2B 40 00 19 40 40 00
(  .  .  .  ]  v  â  ~  .  .  .  .  —  )  M  +  .  .  .  .  ‰  õ  ì  ~  .  .  .  .  .  .  .  .
.  .  .  .  .  .  .  .  ê  8  .  .  .  +  @  .  û  ?  @  .  Â  C  @  .  0  @  @  .  *  ¤  P  .
Í  Ò  P  .

Posted: Mon 17 Oct 2011 10:58
by AlexP
Hello,

We cannot reproduce the problem.
We've checked this problem using FastMM and EurekaLog, and we could not find any memory leaks.
Please send a small sample demonstrating the problem including the script to create and fill the table to alexp*devart*com.