Watch, Follow, &
Connect with Us

Please visit our new home

Public Report
Report From: Delphi-BCB/AddOn/TChart/TDBChart    [ Add a report in this area ]  
Report #:  122844   Status: Closed
[TeeChart Lite] Memory leaks in TDBChart
Project:  Delphi Build #:  19.0.14356.6604
Version:    19.2 Submitted By:   Ludek Stauber
Report Type:  Crash / Data loss / Total failure Date Reported:  2/28/2014 7:31:12 AM
Severity:    Serious / Highly visible problem Last Updated: 4/15/2014 6:31:28 PM
Platform:    All versions Internal Tracking #:   48149
Resolution: Fixed (Resolution Comments) Resolved in Build: : XE6
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
There always comes an memory leaks, if you close a form with TDBChart on it, when the series datasets are open.

(suppose using the advanced memory manager FastMM4 in full debug mode) also many memoryleaks appear.
Steps to Reproduce:
Compile, run and close the attached application

program dbcharttestproj;

  dbchartform in 'dbchartform.pas' {Form1};

{$R *.res}

  ReportMemoryLeaksOnShutdown := True;
  Application.MainFormOnTaskbar := True;
  Application.CreateForm(TForm1, Form1);
call "dataset.close" for all dataset assigned to chart series.
than you get "only" the memory leaks.

Tomohiro Takahashi at 2/28/2014 4:03:15 PM -
Does your issue occur with update version, "TeeChart Lite for RAD Studio, Delphi, C++Builder XE5 Update 2" ?

Ludek Stauber at 3/2/2014 11:46:03 PM -
No, that was the first thing I tried.

Ludek Stauber at 3/2/2014 11:49:28 PM -
Perhaps my reply was not clear enough: It DOES occur with that updated version.

Tomohiro Takahashi at 3/3/2014 12:19:45 AM -
>There always comes an Access Violation exception, if you close a form with TDBChart on it,
If I comment out 'FastMM4' at uses section, I can not reproduce your issue with the update version of TeeeChart Lite.
program dbcharttestproj;


So, I modified [Title] and [DEscription], the opened this report.

Ludek Stauber at 3/3/2014 3:07:16 AM -
Not good. You don't think, that the full debug mode feature of fastmm4 memory manager is wrong, do you REALLY? I'm using it daily for years and have NEVER seen any false alerts...

without fastmm4 full debug mode you are just lucky - but you are still accessing block of freed memory, which (often) still contains the old data :/

code, that depends on data in freed memory blocks is definitely buggy.

David Berneda at 3/3/2014 8:53:49 AM -
Leaks are probably caused by another bug. A new update will be available soon.
A workaround is described at QC122729

Ludek Stauber at 4/9/2014 2:30:21 AM -
Where can I download this update? The workaround would take too much time to implement it everywhere, perhaps also pretty dangerous, if the series are dynamically created(?)

Server Response from: ETNACODE01