initObjectClass() calls attachObjectInterface() twice. This results in 10 objects being replaced during startup, which are 10 objects found unreachable at first GC run.
There's a total of 12 objects unreachable at first GC run, which I'm trying to figure out. One thing: I did expect these kind of replacements to throw an abort or similar, which was one of the reasons for using init_member rather than set_member in initialization code. This didn't happen, so would be worth inspecting why as that might help figuring out the left-over 2. Note that when building with fileio extension enabled the number of unreachable objects at first GC run is higher so it does make sense to have a way to catch such programmatic errors. I'm on a very slow connection so feel free to commit a fix for the double attachObjectInterface. Thanks. --strk; () Free GIS & Flash consultant/developer /\ http://strk.keybit.net/services.html _______________________________________________ Gnash-dev mailing list Gnash-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnash-dev
