Page 1 of 1

Bug with FireDAC datasets

Posted: Wed 13 Jul 2016 04:52
by burdian
Hello,

Delphi 10 Seattle win32, VirtualDAC 10.0, Win 10 x64

When using VirtualDAC with FireDAC datasets I get memory leaks, sometimes AV at memory manager. Sometimes closing main form only hide appl, appl remains in memory.

Samle appl is sent to [email protected] with subject Sometimes closing main form only hide appl, appl remains in memory.

TIA and best regards
Branko

Re: Bug with FireDAC datasets

Posted: Wed 13 Jul 2016 07:09
by AlexP
Hello,

We can't reproduce the problem. Please describe the steps to reproduce the situation. Also specify the memory manager you are using for detecting memory leaks.

Re: Bug with FireDAC datasets

Posted: Wed 13 Jul 2016 07:18
by burdian
Hello,

1) Samle appl was sent to [email protected]. Just click on "Open / close" button and close appl.
2) Default Delphi 10 MM

Re: Bug with FireDAC datasets

Posted: Thu 14 Jul 2016 12:18
by AlexP
Specify the memory manager you are using for detecting memory leaks.

Re: Bug with FireDAC datasets

Posted: Thu 14 Jul 2016 19:01
by burdian
As I have already answered - memory leaks are detecting by default Delphi 10 memory manager. Memory leaks detecting is enabled with code

Code: Select all

initialization
  System.ReportMemoryLeaksOnShutdown := True;
I get the report below:

An unexpected memory leak has occurred. The unexpected small block leaks are:
1 - 12 bytes: TObject x 1
13 - 20 bytes: TFDExpressionManager x 1, UnicodeString x 143
21 - 28 bytes: UnicodeString x 144
29 - 36 bytes: EAccessViolation x 2, UnicodeString x 42
37 - 44 bytes: TFDExpressionFunctionDesc x 119, UnicodeString x 12
45 - 52 bytes: UnicodeString x 4
61 - 68 bytes: Unknown x 162
93 - 100 bytes: TFDStringList x 2
173 - 188 bytes: UnicodeString x 2
1645 - 1804 bytes: Unknown x 1

Re: Bug with FireDAC datasets

Posted: Fri 15 Jul 2016 09:06
by AlexP
As I wrote you earlier, the issue is not reproduced when using either the standard memory manager or FastMM, or EurekaLog. We use Seattle with Update 1.

P.S. Judging by the log you provided, AV and MemoryLeak occur in FireDAC

Re: Bug with FireDAC datasets

Posted: Fri 15 Jul 2016 12:53
by burdian
AlexP wrote:We use Seattle with Update 1.
Me too.
Are you launch the demo appl I sent you?
I get memory leaks and AV also with Delhi XE7 and XE4!

Re: Bug with FireDAC datasets

Posted: Mon 18 Jul 2016 12:40
by AlexP
The issue is not reproduced on your project in any of studios. Please provide also the dproj project file. The case may occur due to the project settings.

Re: Bug with FireDAC datasets

Posted: Mon 18 Jul 2016 19:21
by burdian
Sent to support*devart*com

Re: Bug with FireDAC datasets

Posted: Thu 21 Jul 2016 08:25
by AlexP
Please send your dproj again to alexp*devar*com.

Re: Bug with FireDAC datasets

Posted: Mon 03 Oct 2016 05:23
by burdian
I found what causes memory leaks: Embarcadero\Studio\17.0\bin\SQLite3.dll

Re: Bug with FireDAC datasets

Posted: Tue 04 Oct 2016 11:48
by AlexP
Check this behavior on the standard SQLite library: http://sqlite.org/download.html

Re: Bug with FireDAC datasets

Posted: Fri 14 Oct 2016 13:33
by burdian
Yes, with standard sqlite.dll no memory leaks. I just wanted inform you where / why memory leeks occours.

Re: Bug with FireDAC datasets

Posted: Mon 24 Apr 2017 09:07
by MaximG
When developing and testing our products to work with SQLite we use only standard SQLite library available on the official project site : http://sqlite.org