[...] > - How does you ensure that your thread pool threads finalize the > objects? AFAIK there is no way to explicitly dispose mapped UNO objects.
IIRC the problem is that releasing the (proxied, native) destination object blocks the finalizer, and causes an out of memory condition. So the release of the binary uno_Interface in Java_com_sun_star_bridges_jni_1uno_JNI_1proxy_finalize__J() (jni_java2uno.cxx) has to be performed by another thread. Another point: Has anyone guestimations whether and how much this hurts performance? I can think of a lot of release calls, and when the uno_Interface handle has to be passed to another thread, more sync is needed than before. We should make this release-call handling optional/configurable, do we? -Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
