geoffsmith82 / delphi-javascript

Automatically exported from code.google.com/p/delphi-javascript
5 stars 2 forks source link

A lot of memory leaks #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
Run the demo program with the following line in the dpr
  ReportMemoryLeaksOnShutdown := true;

What is the expected output? What do you see instead?
I'm expect no memory leaks but I see a lot of memory leaks.

What version of the product are you using? On what operating system?
Delphi XE2

Please provide any additional information below.
I'm using the last trunk version

Original issue reported on code.google.com by daniele....@gmail.com on 23 Jul 2012 at 2:57

GoogleCodeExporter commented 8 years ago
The change for this is done now.

Original comment by n.ame...@gmail.com on 1 Oct 2012 at 1:25

GoogleCodeExporter commented 8 years ago
Thank you for your work. However, using the demo project I still see a lot of 
memory leaks in XE3 (not tried in XE2)

Original comment by daniele....@gmail.com on 9 Nov 2012 at 11:40

Attachments:

GoogleCodeExporter commented 8 years ago
I doubt if reported leaks are true for example JSExcludeAttribute is been 
created from the compiler, and initialized also, there is no way for the 
developer to free such a class if i am not wrong, also many others issues 
reported are related to rtl nothing to do on my end for such reports (rtl 
specific)

Original comment by n.ame...@gmail.com on 9 Nov 2012 at 1:20

GoogleCodeExporter commented 8 years ago
Attributes are mantained by the RTTIPool. So problably that mleak depends on 
another mkeak. It seems that that last leaked TObjectDictionary<Pointer, 
TRTTIObject> had a reference to an object managed by the RTTIPool. IMHO problem 
is there.

Thank you for your response

Original comment by daniele....@gmail.com on 9 Nov 2012 at 2:17

GoogleCodeExporter commented 8 years ago
Truth is that i did apply a fix also where rtti context was not free but even 
then memory leaks are still there.....which makes me almost sure that rtl is 
the problem for some reason here...

Original comment by n.ame...@gmail.com on 11 Nov 2012 at 8:10