Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 443 - [TJ71015145] We used SLEAK to capture the non-disposed Resources. 1. started your...
Summary: [TJ71015145] We used SLEAK to capture the non-disposed Resources. 1. started ...
Status: RESOLVED FIXED
Alias: None
Product: Java TeeChart
Classification: Unclassified
Component: Chart (show other bugs)
Version: unspecified
Hardware: All All
: Normal enhancement
Target Milestone: ---
Assignee: Steema Issue Manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-10 10:49 EDT by yeray alonso
Modified: 2016-04-12 04:38 EDT (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yeray alonso 2013-11-20 12:16:56 EST
We used SLEAK to capture the non-disposed Resources.
1. started your Graph and keept it running for some time
2. created a snapshot from the current SWT-Resources by SLEAK
3. called chart.dispose() Method
4. Created a snapshot again and compared the differences
we found there are lot of GC objects,Font objects and color objects are existing in memory.
I think after creating new GC,old GC reference should be made null.For Color and Font It's better to access from registries.
Below stack trace is about GC object creation
at com.steema.teechart.TChart.prepareGraphics(TChart.java:1187)
at com.steema.teechart.TChart.processMouseMotionEvent(TChart.java:1225).
I think these non disposed resources will lead to performance issues.Is there any way to improve performance by disposing above objects.
http://www.teechart.net/support/viewtopic.php?f=10&t=11539&view=unread#unread [created:2010-09-10T09:49:28.000+01:00 reported by:yeray@steema.com reported in version:Build 2.0.0.701 (TeeChart Java)]
Comment 1 marc meumann 2016-04-12 04:38:24 EDT
Further optimisations made. ScrollPager Cursor memory leaks resolved