Hi Andreas,

In the migration from 2_19_1 to 2_20_0, I'm seeing memory leaks that look to be coming from the switch from the built-in array type to using the scriptarray add-on.

I'm using the native calling conventions on x86, with asEP_ALLOW_UNSAFE_REFERENCES set as an engine property.

Regards,
Pratty

[Edited by - pratty on December 16, 2010 6:20:11 PM]

The array add-on and the built-in array had practically identical implementation, so it is unlikely that this switch is the cause of the memory leak.

Are you invoking the garbage collector? It could just be that the array can potentially form a circular reference, in which case the garbage collector must be invoked to free the object.

Can you identify a scenario where the memory leak happens? Perhaps reproduce it with a small script that I can add to my regression test suite?

ok, I'll see if I can come up with a test case.