On 15/08/12 15:27, David Matthews wrote:
On 13/08/2012 22:47, Phil Clayton wrote:
According to profiling messages that I'm generating, when a stand-alone
executable terminates, any remaining finalizers (added with
CInterface.setFinal) are not run. Consequently, resources that should
be freed ma
On 14/08/12 15:47, Matthew Fluet wrote:
On Mon, Aug 13, 2012 at 5:47 PM, Phil Clayton wrote:
This can be worked around easily, for example by creating a variant of
PolyML.export that adds a final PolyML.fullGC to the exported function (for
both normal and exception paths). However, there is th
On 13/08/2012 22:47, Phil Clayton wrote:
According to profiling messages that I'm generating, when a stand-alone
executable terminates, any remaining finalizers (added with
CInterface.setFinal) are not run. Consequently, resources that should
be freed may not be. I think I would probably expect
On Mon, Aug 13, 2012 at 5:47 PM, Phil Clayton wrote:
> This can be worked around easily, for example by creating a variant of
> PolyML.export that adds a final PolyML.fullGC to the exported function (for
> both normal and exception paths). However, there is the question of
> whether, on terminati
According to profiling messages that I'm generating, when a stand-alone
executable terminates, any remaining finalizers (added with
CInterface.setFinal) are not run. Consequently, resources that should
be freed may not be. I think I would probably expect the semantics of
finalizers to be such
