I think I discovered another issue. Not sure if you are already aware of it. Don't remember it being reported before.
Seems like using heaptrc feature (memory leak reporting) with refc-compiler leads to program crashing on exit. In particular, it appears that heaptrc starts reporting memory leaks earlier than refcounted objects get released Not like it is a big problem now. If desired, one can check if refcounted objects leak or not by keeping a global counter variable for each base class (call InterlockedIncrement in constructor; call InterlockedDecrement in destructor; then write count in finalization section of unit) 06.11.2014, 00:02, "Sven Barth" <[email protected]>: > Am 05.11.2014 21:55 schrieb <[email protected]>: >> >> Not bad. I confirm that both Lazarus 1.3 and variables of refcounted type >> declared in another unit work now. > > Good to know :) > >> I wanted to assemble some prototype application with refcounted objects to >> see how would such feature behave in a more or less complex program; but in >> spite of lack of free time I am not sure how much time it will take > > Take your time. The branch is not going anywhere for now as I first want to > finish my work on packages, generic methods and maybe some other features > like extended RTTI, invoke, etc. :) > > Regards, > Sven > , > > _______________________________________________ > fpc-devel maillist - [email protected] > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
